Terminals Command line arguments

List of available switches

Examples

• Connect to a Single machine:

terminals /url:trm://server
terminals /v:server

• Connect to machines stored in favorites named "server" and "server1" at once:

terminals /favs:server,server1

• Connect to console on "server" computer:

terminals /v:server /c

• Connect to Single, Console, Fullsceen on "server" computer:

terminals /v:server /c /f

• When starting Terminals use file stored at \\serverShare\terminalsFiles\terminals.config:

terminals /config:\\serverShare\terminalsFiles\terminals.config

• Windows remote desktop (RDP)
• VNC
• VMRC
• SSH
• Telnet
• RAS
• ICA Citrix
• HTTP and HTTPs based viewers 

• Windows remote desktop (RDP)
• VNC
• VMRC
• SSH
• Telnet
• RAS
• ICA Citrix
• HTTP and HTTPs based viewers 

• Windows remote desktop (RDP)
• VNC
• VMRC
• SSH
• Telnet
• RAS
• ICA Citrix
• HTTP and HTTPs based viewers 

• Windows remote desktop (RDP)
• VNC
• VMRC
• SSH
• Telnet
• RAS
• ICA Citrix
• HTTP and HTTPs based viewers 

How to organize favorites

Manage Groups (Tags)

• "New Tag": If you need create new Tag, type its name here and click on green button close to it. New Tag will be listed in available
• "Connection Tags": Here are listed all Tags associated to this connection. Button on right side removes selected Tag from this list. To add new Tags use text box above or select existing one from text box bellow.
• "All available Tags": Lists all Tags defined on all connections. If you want to show more connections under the same Tag, select one from this list and click green button on right side or double click on it.

Import favorites

Search for computers servicing remote control protocol

• Scan Active Directory: If your computer is member of Microsoft Active Directory, you can search the active directory for computer entries. Later you can select computers in results list and create favorites for them.
• Scan Network using port scanner: This feature offers you to scan all IP addresses in required range for known services. By default your IP address range is selected and all services used by Terminals are searched.
• Direct connect to other Terminals

Grouping connections

How to organize favorites

Manage Groups (Tags)

• "New Tag": If you need create new Tag, type its name here and click on green button close to it. New Tag will be listed in available
• "Connection Tags": Here are listed all Tags associated to this connection. Button on right side removes selected Tag from this list. To add new Tags use text box above or select existing one from text box bellow.
• "All available Tags": Lists all Tags defined on all connections. If you want to show more connections under the same Tag, select one from this list and click green button on right side or double click on it.

Import favorites

Search for computers servicing remote control protocol

• Scan Active Directory: If your computer is member of Microsoft Active Directory, you can search the active directory for computer entries. Later you can select computers in results list and create favorites for them.
• Scan Network using port scanner: This feature offers you to scan all IP addresses in required range for known services. By default your IP address range is selected and all services used by Terminals are searched.
• Direct connect to other Terminals

Grouping connections

Developer guide

Continuous integration

• There is a public Team City server configured for our project at: ...
• Use Login as Guest on Login page
• These builds shouldn't be used as public available development builds (beta or RC)

Last Successful builds:

• Latest Binaries: http://goo.gl/bTlqr
• Unit tests build: http://goo.gl/nFdxs

Application life cycle

• To publish release version, the application version should be updated in Setup project and in Program startup object
• Releases are marked with label. If you want to rollback to previous version load selected version release label
• Tasks have iteration path "Terminals" until there is at least one related checkin. Then change the iteration path to the current development version
• When fixing an issue, mark it as Fixed (not as Closed). Task is closed as a part of release, if there are no comments otherwise it is shifted to next version.

Cooperation rules

• Miguel de Icaza has a good post on Open Source Contribution Etiquette that is worth reading, as the guidance he gives applies well to Terminals (inspired by Nuget project).
• Don't keep your checkouts long time, use Shelve sets instead
• Pickup from task stack only task, which you are able to solve in no more than two months
• Always associate check-in change set with task, if your check in is related to it
• In case of formating make two separate checkins: one which holds only code formating changes, second with fix/feature changes

Project structure

• Current development tool is Visual Studio 2010 with .NET C#.
• The main solution project is configured to target .NET framework 4. But there are other external projects, which are still targeting .NET 2.0. Don't change the target framework for them.
• For Logging the Log4Net is configured. Log files are stored under application Logs subdirectory.
• To build the release setup use the "Distribution release" solution configuration. For general development use standard debug and release.
• Output directory is default directory under the Terminals project.
• Put all localize able resources under the Localization directory in resource file stored there.
• The latest development branch is stored under "Main\Sources"
• To create user branch create your own under "FeatureBranches" directory and branch allways whole main subtree
• All extrenal components and other resources like images should be stored under "Resources" directory in its branch

External components

• SSH protocol from Granados project (actually developed as Poderosa)
• Terminal emulator control for ssh and telnet ( Terminal control)
• Amazon S3 component (from Amazon SDK Amazon SDK for .NET)
• zLib compression library (zLib)
• VNC client library (VncSharp)
• Log4Net (Log4Net)
• Packet manipulation library (SharpPcap)
• ICA Citrix component
• RDP imported as activeX component

Coding rules

• Use Visual Studio 2010 default settings or similar settings in another editor.
• For developer who are using Resharper, there is a Team shared configuration file for coding rules. Don't change this file, if you want to apply some rules. Discuss it first within the team.
• Indents are 4 spaces. You can use Productivity Power Tools for VS to convert tab characters into spaces.
• Fields should be declared private and above all methods.
• Put curly brackets on a new line and close it in the same indentation.
• Keep classes small up to maximum 500 lines
• Keep methods small up to maximum 35 lines
• Use usings as much as possible and remove not used usings
• When using an if condition with one statement, put the statement on the next line.

if (true)
       DoSomething();

• When using an if condition with one statement after if condition and else condition, curly brackets are optional.

if(true)
       DoSomething();
   else
       DoSomethingElse();

• When using an if condition with curly brackets, use curly brackets for all attached conditions

if (true)
   {
       x++;
       DoSomething();
   }
   else
   {
       DoSomethingElse();
   }

• After an if, while, for each or other conditions that can use curly brackets, leave an empty line.

if (true)
      DoSomething();

   x++;
   foreach(String s in stringArray)
   {
      Debug.Print(s);
   }
   
   DoTheNextThing();

• Use String.Format when possible.
• Use String.Empty instead of "", use String.IsNullOrEmpty() instead of (x == null | x = "").

Developer guide

Continuous integration

• There is a public Team City server configured for our project
• Use Login as Guest on Login page
• These builds shouldn't be used as public available development builds (beta or RC)

Last Successful builds:

• Latest Binaries: http://goo.gl/bTlqr
• Unit tests build: http://goo.gl/nFdxs

Application life cycle

• To publish release version, the application version should be updated in Setup project and in Program startup object
• Releases are marked with label. If you want to rollback to previous version load selected version release label
• Tasks have iteration path "Terminals" until there is at least one related checkin. Then change the iteration path to the current development version
• When fixing an issue, mark it as Fixed (not as Closed). Task is closed as a part of release, if there are no comments otherwise it is shifted to next version.

Cooperation rules

• Miguel de Icaza has a good post on Open Source Contribution Etiquette that is worth reading, as the guidance he gives applies well to Terminals (inspired by Nuget project).
• Don't keep your checkouts long time, use Shelve sets instead
• Pickup from task stack only task, which you are able to solve in no more than two months
• Always associate check-in change set with task, if your check in is related to it
• In case of formating make two separate checkins: one which holds only code formating changes, second with fix/feature changes

Project structure

• Current development tool is Visual Studio 2010 with .NET C#.
• The main solution project is configured to target .NET framework 4. But there are other external projects, which are still targeting .NET 2.0. Don't change the target framework for them.
• For Logging the Log4Net is configured. Log files are stored under application Logs subdirectory.
• To build the release setup use the "Distribution release" solution configuration. For general development use standard debug and release.
• Output directory is default directory under the Terminals project.
• Put all localize able resources under the Localization directory in resource file stored there.
• The latest development branch is stored under "Main\Sources"
• To create user branch create your own under "FeatureBranches" directory and branch allways whole main subtree
• All extrenal components and other resources like images should be stored under "Resources" directory in its branch

External components

• SSH protocol from Granados project (actually developed as Poderosa)
• Terminal emulator control for ssh and telnet ( Terminal control)
• Amazon S3 component (from Amazon SDK Amazon SDK for .NET)
• zLib compression library (zLib)
• VNC client library (VncSharp)
• Log4Net (Log4Net)
• Packet manipulation library (SharpPcap)
• ICA Citrix component
• RDP imported as activeX component

Coding rules

• Use Visual Studio 2010 default settings or similar settings in another editor.
• For developer who are using Resharper, there is a Team shared configuration file for coding rules. Don't change this file, if you want to apply some rules. Discuss it first within the team.
• Indents are 4 spaces. You can use Productivity Power Tools for VS to convert tab characters into spaces.
• Fields should be declared private and above all methods.
• Put curly brackets on a new line and close it in the same indentation.
• Keep classes small up to maximum 500 lines
• Keep methods small up to maximum 35 lines
• Use usings as much as possible and remove not used usings
• When using an if condition with one statement, put the statement on the next line.

if (true)
       DoSomething();

• When using an if condition with one statement after if condition and else condition, curly brackets are optional.

if(true)
       DoSomething();
   else
       DoSomethingElse();

• When using an if condition with curly brackets, use curly brackets for all attached conditions

if (true)
   {
       x++;
       DoSomething();
   }
   else
   {
       DoSomethingElse();
   }

• After an if, while, for each or other conditions that can use curly brackets, leave an empty line.

if (true)
      DoSomething();

   x++;
   foreach(String s in stringArray)
   {
      Debug.Print(s);
   }
   
   DoTheNextThing();

• Use String.Format when possible.
• Use String.Empty instead of "", use String.IsNullOrEmpty() instead of (x == null | x = "").

Developer guide

Continuous integration

• There is a public Team City server configured for our project
• Use Login as Guest on Login page
• These builds shouldn't be used as public available development builds (beta or RC)

Last Successful builds:

• Latest Binaries: http://goo.gl/bTlqr
• Unit tests build: http://goo.gl/nFdxs

Application life cycle

• To publish release version:
  • the application version should be updated in Setup project and in Common.AsssemblyInfo.cs
  • Update related build version in Team City nightly builds
  • Keep in mind, that there is new version detected by published release on CodePlex and compared with the build date of the application => Pulish date has to older or equals to the build date.
  • Mark release with label. If you want to rollback to previous version load selected version release label
• TFS Tasks have iteration path "Terminals" until there is at least one related checkin. Then change the iteration path to the current development version
• When fixing an issue, mark it as Fixed (not as Closed). Task is closed as a part of release, if there are no comments otherwise it is shifted to next version.

Cooperation rules

• Miguel de Icaza has a good post on Open Source Contribution Etiquette that is worth reading, as the guidance he gives applies well to Terminals (inspired by Nuget project).
• Don't keep your checkouts long time, use Shelve sets instead
• Pickup from task stack only task, which you are able to solve in no more than two months
• Always associate check-in change set with task, if your check in is related to it
• In case of formating make two separate checkins: one which holds only code formating changes, second with fix/feature changes

Project structure

• Current development tool is Visual Studio 2010 with .NET C#.
• The main solution project is configured to target .NET framework 4. But there are other external projects, which are still targeting .NET 2.0. Don't change the target framework for them.
• For Logging the Log4Net is configured. Log files are stored under application Logs subdirectory.
• To build the release setup use the "Distribution release" solution configuration. For general development use standard debug and release.
• Output directory is default directory under the Terminals project.
• Put all localize able resources under the Localization directory in resource file stored there.
• The latest development branch is stored under "Main\Sources"
• To create user branch create your own under "FeatureBranches" directory and branch allways whole main subtree
• All extrenal components and other resources like images should be stored under "Resources" directory in its branch

External components

• SSH protocol from Granados project (actually developed as Poderosa)
• Terminal emulator control for ssh and telnet ( Terminal control)
• Amazon S3 component (from Amazon SDK Amazon SDK for .NET)
• zLib compression library (zLib)
• VNC client library (VncSharp)
• Log4Net (Log4Net)
• Packet manipulation library (SharpPcap)
• ICA Citrix component
• RDP imported as activeX component

Coding rules

• Use Visual Studio 2010 default settings or similar settings in another editor.
• For developer who are using Resharper, there is a Team shared configuration file for coding rules. Don't change this file, if you want to apply some rules. Discuss it first within the team.
• Indents are 4 spaces. You can use Productivity Power Tools for VS to convert tab characters into spaces.
• Fields should be declared private and above all methods.
• Put curly brackets on a new line and close it in the same indentation.
• Keep classes small up to maximum 500 lines
• Keep methods small up to maximum 35 lines
• Use usings as much as possible and remove not used usings
• When using an if condition with one statement, put the statement on the next line.

if (true)
       DoSomething();

• When using an if condition with one statement after if condition and else condition, curly brackets are optional.

if(true)
       DoSomething();
   else
       DoSomethingElse();

• When using an if condition with curly brackets, use curly brackets for all attached conditions

if (true)
   {
       x++;
       DoSomething();
   }
   else
   {
       DoSomethingElse();
   }

• After an if, while, for each or other conditions that can use curly brackets, leave an empty line.

if (true)
      DoSomething();

   x++;
   foreach(String s in stringArray)
   {
      Debug.Print(s);
   }
   
   DoTheNextThing();

• Use String.Format when possible.
• Use String.Empty instead of "", use String.IsNullOrEmpty() instead of (x == null | x = "").

• Windows remote desktop (RDP)
• VNC
• VMRC
• SSH
• Telnet
• RAS
• ICA Citrix
• HTTP and HTTPs based viewers 

Whats new with Terminals?

• Windows remote desktop (RDP)
• VNC
• VMRC
• SSH
• Telnet
• RAS
• ICA Citrix
• HTTP and HTTPs based viewers 

Features and Screen shots

User interface

• Multi tab interface
• Open terminal in full screen, switch between full screen mode
• Resizable terminal window
• Attached and dettached Windows
• Connections history
• Customizable toolbars
• Open custom application from Terminals window
• Toolbar for computer control panel applets

Connection options

• Select one of available protocols and custom port
• Terminal fonts and colors (ssh)
• Automatically connect with stored credentials
• Custom connection icon
• Screen size and screen mode (RDP)
• Before connection scripts
• Organize connections by Tags

Manage favorites

• Import from other file formats
• Search computers in Active directory
• Search computers in your network by IP addresses
• Automatic import RDP connection from registry

Networking tools

• Ping
• Tracert
• DNS tools
• Wake on lan
• Port scanner
• Shares
• Services
• Who is?
• Interfaces

Credentials manager

• Store your connections credentials in secured file, so you don't have to retype them when connecting
• Reuse them for more then one connection
• Define default connection credentials

Capture manager

• Create screen shots of your terminal sessions
• Manage and view captured pictures
• Automated capture for all opened sessions
• Publish your captures gallery on Flicker

Application options

• Define connections interface behavior
• Set application master password and other security
• Define settings files directory
• Define capture behavior
• Synchronize your configuration to Amazon S3

Features and Screen shots

User interface

• Multi tab interface
• Open terminal in full screen, switch between full screen mode
• Resizable terminal window
• Attached and dettached Windows
• Connections history
• Customizable toolbars
• Open custom application from Terminals window
• Toolbar for computer control panel applets

Connection options

• Select one of available protocols and custom port
• Terminal fonts and colors (ssh)
• Automatically connect with stored credentials
• Custom connection icon
• Screen size and screen mode (RDP)
• Before connection scripts
• Organize connections by Tags

Manage favorites

• Import from other file formats
• Search computers in Active directory
• Search computers in your network by IP addresses
• Automatic import RDP connection from registry

Networking tools

• Ping
• Tracert
• DNS tools
• Wake on lan
• Port scanner
• Shares
• Services
• Who is?
• Interfaces

Credentials manager

• Store your connections credentials in secured file, so you don't have to retype them when connecting
• Reuse them for more then one connection
• Define default connection credentials

Capture manager

• Create screen shots of your terminal sessions
• Manage and view captured pictures
• Automated capture for all opened sessions
• Publish your captures gallery on Flicker

Application options

• Define connections interface behavior
• Set application master password and other security
• Define settings files directory
• Define capture behavior
• Synchronize your configuration to Amazon S3

• Windows remote desktop (RDP)
• VNC
• VMRC
• SSH
• Telnet
• RAS
• ICA Citrix
• HTTP and HTTPs based viewers 

Developer guide

Continuous integration

• There is a public Team City server configured for our project
• Use Login as Guest on Login page
• These builds shouldn't be used as public available development builds (beta or RC)

Last Successful builds:

• Latest Binaries: http://goo.gl/bTlqr
• Unit tests build: http://goo.gl/nFdxs

Application life cycle

• To publish release version:
  • the application version should be updated in Setup project and in Common.AsssemblyInfo.cs
  • Update related build version in Team City nightly builds
  • Keep in mind, that there is new version detected by published release on CodePlex and compared with the build date of the application => Pulish date has to older or equals to the build date.
  • Mark release with label. If you want to rollback to previous version load selected version release label
• TFS Tasks have iteration path "Terminals" until there is at least one related checkin. Then change the iteration path to the current development version
• When fixing an issue, mark it as Fixed (not as Closed). Task is closed as a part of release, if there are no comments otherwise it is shifted to next version.

Cooperation rules

• Miguel de Icaza has a good post on Open Source Contribution Etiquette that is worth reading, as the guidance he gives applies well to Terminals (inspired by Nuget project).
• Don't keep your checkouts long time, use Shelve sets instead
• Pickup from task stack only task, which you are able to solve in no more than two months
• Always associate check-in change set with task, if your check in is related to it
• In case of formating make two separate checkins: one which holds only code formating changes, second with fix/feature changes

Project structure

• Current development tool is Visual Studio 2010 with .NET C#.
• The main solution project is configured to target .NET framework 4. But there are other external projects, which are still targeting .NET 2.0. Don't change the target framework for them.
• For Logging the Log4Net is configured. Log files are stored under application Logs subdirectory.
• To build the release setup use the "Distribution release" solution configuration. For general development use standard debug and release.
• Output directory is default directory under the Terminals project.
• Put all localize able resources under the Localization directory in resource file stored there.
• The latest development branch is stored under "Main\Sources"
• To create user branch create your own under "FeatureBranches" directory and branch allways whole main subtree
• All extrenal components and other resources like images should be stored under "Resources" directory in its branch
• Temporar solution for new setup created in WIX is present in the sources directory and will be removed after the setup is able to replace current setup

External components

• SSH protocol from Granados project (actually developed as Poderosa)
• Terminal emulator control for ssh and telnet ( Terminal control)
• Amazon S3 component (from Amazon SDK Amazon SDK for .NET)
• zLib compression library (zLib)
• VNC client library (VncSharp)
• Log4Net (Log4Net)
• Packet manipulation library (SharpPcap)
• ICA Citrix component
• RDP imported as activeX component
• Setup WIX toolkit (WIX Toolkit)

Coding rules

• Use Visual Studio 2010 default settings or similar settings in another editor.
• For developer who are using Resharper, there is a Team shared configuration file for coding rules. Don't change this file, if you want to apply some rules. Discuss it first within the team.
• Indents are 4 spaces. You can use Productivity Power Tools for VS to convert tab characters into spaces.
• Fields should be declared private and above all methods.
• Put curly brackets on a new line and close it in the same indentation.
• Keep classes small up to maximum 500 lines
• Keep methods small up to maximum 35 lines
• Use usings as much as possible and remove not used usings
• When using an if condition with one statement, put the statement on the next line.

if (true)
       DoSomething();

• When using an if condition with one statement after if condition and else condition, curly brackets are optional.

if(true)
       DoSomething();
   else
       DoSomethingElse();

• When using an if condition with curly brackets, use curly brackets for all attached conditions

if (true)
   {
       x++;
       DoSomething();
   }
   else
   {
       DoSomethingElse();
   }

• After an if, while, for each or other conditions that can use curly brackets, leave an empty line.

if (true)
      DoSomething();

   x++;
   foreach(String s in stringArray)
   {
      Debug.Print(s);
   }
   
   DoTheNextThing();

• Use String.Format when possible.
• Use String.Empty instead of "", use String.IsNullOrEmpty() instead of (x == null | x = "").

User documentation

Key application terms:

• Connection - session between computer, which offers remote control, and your Terminals application
• Terminal - text window, which can be used for not GUI remote control protocols like Telnet or SSH
• Favorite - stored configuration, which allows you to connect to one service on one server using one user login
• Tag - text associated with one or more favorites, which allows you to group your favorites into logical groups visible in tree
• Group - set of favorites used for batch connections
• Shortcut - stored configuration, which allows you to start script or application directly from Terminals application. By default Terminals comes with shortcuts to Microsoft management console and Control panel applets
• Capture - stored screen picture of your running connection
• Protocol - type of remote control service offered by server you want to connect to
• Credentials - authentication informations (Domain, user name and password). Note, that you don't have to store your passwords. For more details check the documentation.

How to ...

• Manage connections
  • Create connection
  • Check why i can't connect
  • Move connection to the other monitor
  • Configure connection share
• Manipulate with connection credentials
  • Define custom connection credentials
  • Reuse stored credentials for more connections
  • Protect my connections with master password
• Organize favorites
  • Manage Tags and Groups
  • Import favorites
  • Search for computers servicing remote control protocol
• Capture connection screen
• Configure application data
  • Backup and restore settings files
  • Store data in SQL database
• Start Terminals using Command line arguments
• Select proper Application Option

User documentation

Key application terms:

• Connection - session between computer, which offers remote control, and your Terminals application
• Terminal - text window, which can be used for not GUI remote control protocols like Telnet or SSH
• Favorite - stored configuration, which allows you to connect to one service on one server using one user login
• Tag - text associated with one or more favorites, which allows you to group your favorites into logical groups visible in tree
• Group - set of favorites used for batch connections
• Shortcut - stored configuration, which allows you to start script or application directly from Terminals application. By default Terminals comes with shortcuts to Microsoft management console and Control panel applets
• Capture - stored screen picture of your running connection
• Protocol - type of remote control service offered by server you want to connect to
• Credentials - authentication informations (Domain, user name and password). Note, that you don't have to store your passwords. For more details check the documentation.

How to ...

• Manage connections
  • Create connection
  • Check why i can't connect
  • Move connection to the other monitor
  • Configure connection share
• Manipulate with connection credentials
  • Define custom connection credentials
  • Reuse stored credentials for more connections
  • Protect my connections with master password
• Organize favorites
  • Manage Tags and Groups
  • Import favorites
  • Search for computers servicing remote control protocol
• Capture connection screen
• Configure application data
  • Backup and restore settings files
  • Store data in SQL database
• Start Terminals using Command line arguments
• Select proper Application Options