Skip to content

File extension and path checks need to take into account case-sensitive file systems #3218

Closed

Description

https://github.com/PowerShell/PowerShell/search?utf8=%E2%9C%93&q=ordinalignorecase+getextension&type=Code

(query may not be complete)

On Linux/Mac, we should follow any precedent dotnet has already defined for assemblies (in case there's foo.dll and foo.DLL)

Activity

  1. iSazonov commented on Feb 27, 2017

    @iSazonov
    Collaborator

    I believe we should consider not only extensions but paths.

  2. changed the title [-]File extension checks need to take into account case-sensitive file systems[/-] [+]File extension and path checks need to take into account case-sensitive file systems[/+] on Feb 27, 2017
  3. SteveL-MSFT commented on Feb 28, 2017

    @SteveL-MSFT
    MemberAuthor

    Need to take in account that fat32 mounted on Linux recognizes the case-insensitiveness

  4. iSazonov commented on Feb 28, 2017

    @iSazonov
    Collaborator

    Steve Lee (@SteveL-MSFT) Linux can mount NTFS too but I don't about case-insensitiveness.

  5. jeffbi commented on Feb 28, 2017

    @jeffbi

    Ilya (@iSazonov) From https://support.microsoft.com/en-us/help/100108/overview-of-fat,-hpfs,-and-ntfs-file-systems :

    Names preserve case, but are not case sensitive. NTFS makes no distinction of filenames based on case.

  6. iSazonov commented on Mar 1, 2017

    @iSazonov
    Collaborator

    jeffbi Thanks! I meant that Linux could have unpredictable implementation 😕

  7. added this to the milestone on Mar 1, 2017
  8. added
    WG-Engine-Providersbuilt-in PowerShell providers such as FileSystem, Certificates, Registry, etc.
    and removed
    WG-Cmdletsgeneral cmdlet issues
    on Mar 5, 2017
  9. modified the milestones: 6.0.0-beta1, on Mar 16, 2017
  10. 11 remaining items

  11. joeyaiello commented on May 15, 2017

    @joeyaiello
    Contributor

    jeffbi: is this fixed by #3441? Or do we just need to take the same system-call based approach throughout more of the codebase?

  12. modified the milestones: , on May 15, 2017
  13. jeffbi commented on May 15, 2017

    @jeffbi

    Joey Aiello (@joeyaiello) No, the code in #3441 is currently used only by the Copy-Item cmdlet.

  14. modified the milestones: , on Sep 18, 2017
  15. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

  16. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

  17. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

  18. microsoft-github-policy-service commented on Nov 23, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Resolution-No ActivityIssue has had no activity for 6 months or moreSize-MultipleWeeksWG-Enginecore PowerShell engine, interpreter, and runtimeWG-Engine-Providersbuilt-in PowerShell providers such as FileSystem, Certificates, Registry, etc.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions