You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: d5bfa37f61

ai/coverage-unknowns

ai/gate3-published-rc7-acceptance

ai/release-5.0.0-rc6

ai/test-coverage-assessment

master

test/transfer

4.2.6

4.2.4

4.2.3

5.0.0-rc7

5.0.0-rc6

5.0.0-rc5

5.0.0-rc4

5.0.0-rc3

5.0.0-rc2

5.0.0-rc1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'd5bfa37f61'

${ noResults }

NTFSSecurity/NTFSSecurity/LinkCmdlets

History

Raimund Andree 7936d9fc71 fix(links): name the items in the errors and continue after an invalid path From the security-reviewer pass over be04cb7..4ee01e5 (Minor 1, 2, and 5, Nit 9): - A path with a character that Windows doesn't allow, such as |, stopped the pipeline in Windows PowerShell, where resolving the path throws an ArgumentException; both cmdlets now write a non-terminating error with the category InvalidArgument, also in PowerShell 7, where AlphaFS rejects the path when it creates the link. - The errors of New-NTFSSymbolicLink for an existing -Path and a missing -Target, and of New-NTFSHardLink for a folder as -Target, named no path. - New-NTFSSymbolicLink checked -Target before -Path, so that the two cmdlets reported different errors for an existing -Path with a missing -Target; both check -Path first now. - The pages list objects with Path and Target as input of their own. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>		3 days ago
..
GetHardLink.cs	fix: write non-terminating errors from the hard link cmdlets on shares and for folders	4 days ago
NewHardLink.cs	fix(links): name the items in the errors and continue after an invalid path	3 days ago
NewSymbolicLink.cs	fix(links): name the items in the errors and continue after an invalid path	3 days ago