How tenScripting Works

tenScripting is distributed as a Microsoft development project.  It contains all of the VB.NET source code that creates the development environnent providing access to the HomeSeer classes.  When you run the tenScripting project it:

Connects to your HomeSeer server to create remote copies of the key HomeSeer classes

Reads both the source files included in the project and scans the executing memory for all copies of HomeSeer scripts that are included in the project.  There are several sample scripts included in the distributed project (SimpleSamples.vb and ComplexSamples.vb).  You add your own scripts to the project for testing.

Populates the drop-down lists with the files, scripts, and methods found in the project.

Once tenScripting is running and connected to HomeSeer, you select the file/script/method that you want to run/debug. You can optionally enter parameters for the method you selected, to be passed to the method when it is run.  When you click on the Run button, the selected script is loaded and the specified parameters are passed to the selected method.  Your script is now running in the development environment.

Instead of manually executing a selected script, you can define triggers that cause a script to be run when a HomeSeer device changes its status or value. 

While tenScripting is running (before, during, and after execution of your script), it monitors and displays any HomeSeer Device changes (Status, Value, DeviceString) and displays these changes in a scrolling list.  In a similar fashion, it displays any records written to the HomeSeer log.  You can also turn on detailed HomeSeer Debug Logging, and easily display the logged records.

Once your script is fully debugged, tenScripting can then easily copy it to your HomeSeer scripts folder via a network share.

The tenScripting program window: