Skip to content

FindFirstFileName and FindNextFileName are available in NanoServer and IoT now, so we should enable the usage of them in powershell core #2349

@daxian-dbw

Description

@daxian-dbw

There are 2 issues to address here

  • The usage of FindFirstFileName and FindNextFileName is disabled in powershell core at https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/namespaces/FileSystemProvider.cs#L7928. Now they are available in NanoServer and IoT in the API set api-ms-win-core-file-l1-2-2, so maybe now it's the time to enable them in powershell core. Note that this API set is not available in .net core packages by default, so we basically need to verify if the kernel32 forwarder on NanoServer and IoT can correctly forward the call to the right API set.
  • (Fixed in Cleanup FileSystemProvider from runtime checks #7655) FileSystemProvider.cs needs to be refactored. I spot 2 things -- (1) GetTarget and InternalGetTarget needs to be refactored as Platform.NonWindowsInternalGetTarget won't be reached at all. (2) runtime checks should be converted to compilation time checks as much as possible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Enhancementthe issue is more of a feature request than a bugResolution-No ActivityIssue has had no activity for 6 months or moreUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Enginecore PowerShell engine, interpreter, and runtime

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions