> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/tasks/tasks/files/delete.md). # Delete Task version: 1.2.0 Required Frends version: 5.5+ Required .NET version: 6.0 Compatible Agents: Crossplatform Source code: ## Task Parameters {% tabs %} {% tab title="Input" %} | Name | Description | | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | | Directory : `String` |

Source directory.


Default: -
Example: c:\temp

| | | Pattern : `String` |

Pattern to match for files. The file mask uses regular expressions, but for convenience, it has special handling for \* and ? wildcards.


Default: "\*\*\Folder\*.xml"
Example: test.txt, test\*.txt, test?.txt, test.(txt | xml), test.\[^t]\[^x]\[^t], ^(?!prof).\*\_test.txt

| | {% endtab %} | | | {% tab title="Options" %} | Name | Description | | ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | UseGivenUserCredentialsForRemoteConnections : `Boolean` |

If set, allows you to give the user credentials to use to delete files on remote hosts.

If not set, the agent service user credentials will be used.

Note: This feature is only possible with Windows agents.


Default: False
Example: true

| | UserName : `String` |

This needs to be of format domain\username


Default: "domain\username"
Example: domain\username

| | 🗝Password : `String` |

Password for the used credentials.


Default: -
Example: testpwd

| | {% endtab %} | | | {% endtabs %} | | ## Task Result | Name | Description | | ------------------------ | ------------------------------------------------------------------------------------------------- | | Files : `List` |

List of file items deleted from directory.
Example: \[test.txt, test2.txt]

| ## Task Changelog Changelog for Task Frends.Files.Delete. ### \[1.2.0] - 2025-03-19 #### Changed * Update packages: Microsoft.Extensions.FileSystemGlobbing 7.0.0 -> 9.0.3 System.ComponentModel.Annotations 4.7.0 -> 5.0.0 System.DirectoryServices 7.0.0 -> 8.0.0 coverlet.collector 3.1.0 -> 6.0.4 Microsoft.NET.Test.Sdk 16.6.1 -> 17.13.0 MSTest.TestAdapter 2.2.7 -> 3.8.3 MSTest.TestFramework 2.2.8 -> 3.8.3 nunit 3.12.0 -> 4.3.2 NUnit3TestAdapter 3.17.0 -> 5.0.0 ### \[1.1.0] - 2025-03-13 #### Fixed * Fixed bug where regex patterns were not handled correctly in file matching. ### \[1.0.0] - 2023-02-13 #### Added * Initial implementation --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.frends.com/tasks/tasks/files/delete.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.