I'm speaking with an potential new partner for Liquit called ThinClient. Hey suggested to me the following change to the ShellAPI.
1. Rename is to be a more prominent function. Examples (Liquit, ...)
2. Make the commands use names instead of Id's
3. Make the Liquit install to add the agent path to the environment variable so from PowerShell and CMD you can direct call the ShellAPI
4. Document the ShellAPI functions on docs.liquit.com
5. Make it a real PowerShell command, that comes with the agent
Benefits for admins can directly trigger installs or repairs from a cmd. Or can send it as a remote command to a device to update or repair a package.
You can run:
ShellAPI.exe package install "Java"
Or better
PS> liquit install java
(this is the way chocolatey is able to!)
| Product | Application Workspace |
I'm speaking with an potential new partner for Liquit called ThinClient. Hey suggested to me the following change to the ShellAPI.
1. Rename is to be a more prominent function. Examples (Liquit, ...)
2. Make the commands use names instead of Id's
3. Make the Liquit install to add the agent path to the environment variable so from PowerShell and CMD you can direct call the ShellAPI
4. Document the ShellAPI functions on docs.liquit.com
5. Make it a real PowerShell command, that comes with the agent
Benefits for admins can directly trigger installs or repairs from a cmd. Or can send it as a remote command to a device to update or repair a package.
You can run:
ShellAPI.exe package install "Java"
Or better
PS> liquit install java
(this is the way chocolatey is able to!)