Skip to content
Thanks a lot!
Request: Command Line Enhancements
Got a problem with Viscosity or need help? Ask here!
Hello.
Here are several things I would like to be improved in Viscocity command line:
1. Besides connect and disconnect commands (http://www.sparklabs.com/support/viswin_command_line/) also have at least status command:
it would be also nice to have these per connection:
2. The explanations of the command line parameters should be shown when ? or Help is used.
3. IMHO, all commands, including connect and disconnect should be send with '/' or '-' prefix, for example:
Here are several things I would like to be improved in Viscocity command line:
1. Besides connect and disconnect commands (http://www.sparklabs.com/support/viswin_command_line/) also have at least status command:
Code: Select all
"... \Viscosity.exe" status "My Connection"
it would be also nice to have these per connection:
Code: Select all
and one that will return all existing connection names
"... \Viscosity.exe" connectiontime "My Connection"
"... \Viscosity.exe" clientip "My Connection"
"... \Viscosity.exe" serverip "My Connection"
Code: Select all
This way it would be much easier to manipulate the connections remotely."... \Viscosity.exe" connections
2. The explanations of the command line parameters should be shown when ? or Help is used.
3. IMHO, all commands, including connect and disconnect should be send with '/' or '-' prefix, for example:
Code: Select all
or
"... \Viscosity.exe" /connect "My Connection"
Code: Select all
regards"... \Viscosity.exe" -connect "My Connection"
Hi tridy,
Please have a look at the following for some more advanced commands - http://www.sparklabs.com/support/viswin_script_control/
We can certainly take your other suggestions on board.
Regards,
Eric
Please have a look at the following for some more advanced commands - http://www.sparklabs.com/support/viswin_script_control/
We can certainly take your other suggestions on board.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Eric wrote:Please have a look at the following for some more advanced commands - http://www.sparklabs.com/support/viswin_script_control/That's really good! Managed to get a PowerShell script running every 5 minutes and checking if it's not in Connected state and then connecting.
Thanks a lot!
3 posts
Page 1 of 1