Skip to content

DataStar Release:

Release Date: 17th June 2020

ClickOnce MSI Installer Chocolatey

Please note DataStar.CmdLine is also available via the Azure Dev Ops Marketplace packaged as a VSIX file. This can be installed into Azure Dev Ops or Team Foundation to provide access to a packaged task or alternatively unzipped to extract the DataStar.CmdLine binaries.


This release depends on Microsoft's .NET Framework 4.7.2 - this should be installed prior to upgrading. You can find the .NET Framework 4.7.2 by following these links:


FEATURE 131 - An enhancement has been applied to better handle reversal scripts where there are dependencies between different component types, for example scripts to manage disable and enabled constraints are typically wrapped around each group which may be fine when running in the normal deployment order, however this may work in a reversal scenario. To solve for this problem you can add an additional tag to the metadata in the enable and disable scripts to tell DataStar to shift the script to the start or end in a reversal scenario so that all the disable constraints run first and all the enable constraints run last - this new metadata tag is optional and only applies to reversals.

-- Metadata: {"static":"true","rollbackShift":"start"}


-- Metadata: {"static":"true","rollbackShift":"end"}

Resolved Issues

DEFECT 129 - Windows 7 was removed from "ClickOnce" as a minimum target as it is no longer supported by Microsoft, however there are still users of this operating system and therefore we have re-instated the ability to install to Windows 7 machines.

DEFECT 127 - Applies to "DataStar.CmdLine" only. When deploying (with reversal enabled) the reversal process generates some temporary files that are stored in the "LocalApplicationData" - when running under a local system account (i.e. as a service) this can cause issues where the temp files cannot be written or read. This results in an error message "Error ADS Error creating compensation scripts: Unable to determine the data type for column...". A workaround is to run the deployment agent as a service account, however a fix has now been applied so that a temporary folder is used.

Back to top