> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/1.2/getting-started/creating-a-content-item/applications.md).

# Applications

First, create a content item and specify that its purpose is **Application** and type is either **Folder** or **Single File**.  Check the "Open after creation" checkbox for convenience.

<figure><img src="/files/aMVotgBgj8fItMc8E5qy" alt=""><figcaption></figcaption></figure>

Next, click "+ New Version" to add a version to the application.  In the application version, specify the  installation command line, and optionally the working directory and success exit codes.

<figure><img src="/files/vxq4OQy42Z4deitoxgKy" alt=""><figcaption></figcaption></figure>

The working directory defaults to the folder containing the extracted content.  If no success codes are specified, the default of "0 3010" will apply.  (Exit code 3010 indicates that a reboot should be performed.)

After the application version has been created, the content for the application can then be uploaded.  Click the "Choose File" button and select either a file or a folder needed for the application.

<figure><img src="/files/Zk8IIboJVh9eHu3EtruC" alt=""><figcaption></figcaption></figure>

Normally, you would use a folder (the entire contents of the folder will be uploaded), but there are instances where a single file would be desired:

* MSI installers where no other files (e.g. transforms) are required.
* Intune app packages (.intunewin files) which can be automatically extracted by DeployR before installation.

### PowerShell wrappers

Applications that are installed with a PowerShell script, set the Installation command line to:

```
pwsh.exe -file .\PowerShellScript.ps1
```

Make sure the PowerShell script is located in the root of the source of the content you uploaded to create this Application Content Item.


---

# 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:

```
GET https://documentation.2pintsoftware.com/deployr/1.2/getting-started/creating-a-content-item/applications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.