Skip to content

Commit f74537e

Browse files
updated command interpreter section
1 parent 55f9d2d commit f74537e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/vm-applications.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ VM application versions are the deployable resource. Versions are defined with t
9595
- Remove string to show how to properly remove the app
9696
- Package file name to use when it's downloaded to the VM
9797
- Configuration file name to be used to configure the app on the VM
98-
- A link to the configuration file for the VM application
98+
- A link to the configuration file for the VM application, which you can include license files
9999
- Update string for how to update the VM application to a newer version
100100
- End-of-life date. End-of-life dates are informational; you'll still be able to deploy VM application versions past the end-of-life date.
101101
- Exclude from latest. You can keep a version from being used as the latest version of the application.
@@ -126,7 +126,7 @@ The default command interpreters are:
126126
- Linux: `/bin/sh`
127127
- Windows: `cmd.exe`
128128

129-
It's possible to use a different interpreter, as long as it's installed on the machine, by calling the executable and passing the command to it. For example, to have your command run in PowerShell on Windows instead of cmd, you can pass `powershell.exe -Command '<powershell commmand>'`
129+
It's possible to use a different interpreter like Chocolatey or PowerShell, as long as it's installed on the machine, by calling the executable and passing the command to it. For example, to have your command run in PowerShell on Windows instead of cmd, you can pass `powershell.exe -Command '<powershell commmand>'`
130130

131131

132132
## How updates are handled

0 commit comments

Comments
 (0)