Compatibility with legacy scripts

As of release 1.2.0 of the toolkit, the prefixes for cmdlets have been changed to 1E from Tachyon to reflect the company rebranding and product renaming. Scripts that use the Tachyon prefix are now referred to as legacy.

You can change the default prefix within the PowerShell manifest file directly, following the process defined below.

Alternatively you can import the toolkit using the following command line:

import-module .\ps1etoolkit.psd1 -force -prefix Tachyon

If you do this, the cmdlets will work with either the new 1E prefix or the legacy Tachyon prefix. For example, set-1eserver or set-tachyonserver should both work after doing this.

Changing the default prefix in the manifest file

For backwards compatibility of your legacy scripts (which use the Tachyon prefix), you can reconfigure the prefix in the PS1EToolkit.psd1 manifest file. First, locate the line which specifies the DefaultCommandPrefix and change 1E to Tachyon as shown below, then save the file. Finally, you must re-import the module.

Due to limitations regarding PowerShell help, the embedded online help for cmdlets will continue to show the 1E prefix in any examples, regardless of the setting for DefaultCommandPrefix, but the cmdlets will all honor the changed setting.

# Default prefix for commands exported from this module. Override the default prefix using Import-Module -Prefix.

    DefaultCommandPrefix = 'Tachyon'