Long file paths

Long file paths – greater than 260 characters – have been a pain to deal with in Windows.

There is an argument that you should avoid file paths of that length but sometimes you don’t have any choice – when you inherit a file structure for instance.

The following cmdlets from the NTFSsecurity module I recently highlighted are designed to work with long file paths.

Copy-Item2
Get-ChildItem2
Get-FileHash2
Get-Item2
Move-Item2
Remove-Item2
Test-Path2

Hopefully, this will make dealing with long file paths easier in the future

Advertisements
This entry was posted in File system, PowerShell v5. Bookmark the permalink.

1 Response to Long file paths

  1. I apologize if this isn’t the place for this thought but since the rollout of PowerShell.Core, what (Richard) has been your favorite IDE for working in PowerShell? Thank you! and cheers!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s