CommenceApp Constructor

public CommenceApp()

Public Sub New

If the constructor fails because either Commence is not running, or Commence is running multiple instances in the same userprofile, an exception is thrown. COM users (VBScript, VBA, etc.) will not get a useful error message. This is a bit of a problem that I am unsure how to solve. We could incorporate a lazy initialization routine and call that as soon as any of the properties are called, then return a more useful error to a consumer, but that is very messy from a .NET point of view.

Note that this behaviour may change in future releases.

Note that if you want to execute a PowerShell of VBScript script, and Commence is started as administrator (or vice-versa), the script will prompt to start another instance of Commence. The userlevel of the user of the assembly must match the userlevel of the Commence instance.