dotnet-apiport icon indicating copy to clipboard operation
dotnet-apiport copied to clipboard
verified publisher icon microsoft

advice on "unsupported" APIs

Open jol64 opened this issue 6 years ago • 1 comments

I ran portability analyzer today, and in essence it spotted usage of the follwing methods being non portable:

  • M:System.IO.DirectoryInfo.GetAccessControl
  • M:System.IO.DirectoryInfo.SetAccessControl(System.Security.AccessControl.DirectorySecurity)
  • M:System.IO.Pipes.NamedPipeServerStream.#ctor(System.String,System.IO.Pipes.PipeDirection,System.Int32,System.IO.Pipes.PipeTransmissionMode,System.IO.Pipes.PipeOptions,System.Int32,System.Int32,System.IO.Pipes.PipeSecurity,System.IO.HandleInheritability,System.IO.Pipes.PipeAccessRights)
  • M:System.IO.Pipes.PipeStream.GetAccessControl
  • M:System.IO.Pipes.PipeStream.SetAccessControl(System.IO.Pipes.PipeSecurity)

I´d definitley expect security aspects to be covered in "Platform Extensions" aka "Windows Compatibility Pack". Is this an issue in analyzer or where can I ask a question to the "Windows Compatibility Pack"?

Thanks, Joachim

jol64 avatar Nov 23 '19 21:11 jol64

@terrajobst Can you advice what's the recommended change for these APIs on .NET Core?

Lxiamail avatar Dec 04 '19 01:12 Lxiamail

Closing as API Port was deprecated in favor of binary analysis in .NET Upgrade Assistant.

terrajobst avatar Nov 15 '22 23:11 terrajobst