* CP-45071: Convert XenCenter build scripts to PowerShell.
* Removed obsolete variable.
* Pass the timestamp server and the certificate thumbprint as parameters to the build and sign scripts.
* Added further logging and made the verbose output of cmdlets optional.
* Updated README.
* Improved script readability.
Signed-off-by: Konstantina Chremmou <Konstantina.Chremmou@cloud.com>
It's meant to delete empty folders on uninstall but it's not applicable in this case, and caused issued if users don't have the correct rights.
Also rename the IDs to better match content
Signed-off-by: Danilo Del Busso <danilo.delbusso@cloud.com>
Also update spacing of controls within the `CustomizeDlg` to take more advantage of the available space
Signed-off-by: Danilo Del Busso <danilo.delbusso@cloud.com>
When an instance of XenCenter is already running, the installer shows the `MsiRMFilesInUse` fragment. Pressing OK within that fragment with the `WixUIRMOption` property set to `UseRM` means that the `RMShutdownAndRestart` event kicks in at the end of the installation.
This happens at the same time as the existing "Launch XenCenter" event (if the matching checkbox is checked), causing in the executable being started twice at about the same time. My guess is that the pipe system is not initialised at that point, and that's how we get two applications.
To avoid this, this commit adds a new custom property: `XS_WixUIRMPressedOk`. This is set to `1` when the user clicks OK on the `WixUIRMOption`. It allows us to know whether or not that dialog was shown at all, as checking `WixUIRMOption` is not possible (it's already set to `UseRM` by default). By checking the value of this property we prevent the "Launch XenCenter" option to be shown if `MsiRMFilesInUse` was shown to the user (and they clicked OK). This applies both in case of a repair and an upgrade from a previous version.
Signed-off-by: Danilo Del Busso <danilo.delbusso@cloud.com>
XenCenter executable was started with elevated privileges even with use of `Impersonate = "yes"`, and `WixShellExecTarget` was actually ignored.
Signed-off-by: Danilo Del Busso <danilo.delbusso@cloud.com>
Also, renamed the placeholder because msbuild converts spaces to underscores
and in debug mode the settings path is different from the one expected.
Signed-off-by: Konstantina Chremmou <Konstantina.Chremmou@cloud.com>
Also renamed the archive classes because they were named after the 3rd
party library used and were confusing.
Signed-off-by: Konstantina Chremmou <konstantina.chremmou@citrix.com>
- Use `BrandConsole` for the name of the app
- Use a localised value for the word `Launch`
- Use `asyncNoWait` when launching the CHC executable
Signed-off-by: Danilo Del Busso <Danilo.Del.Busso@citrix.com>
Previously this was not possible due to XenModel-XenOvfTransport cyclical references.
Signed-off-by: Konstantina Chremmou <konstantina.chremmou@citrix.com>
Since the standalone VNC control was removed, the VNC code has been used only by
the UI project. According to Microsoft's performance guidelines large single
assemblies are preferable to multiple smaller ones.
Signed-off-by: Konstantina Chremmou <konstantina.chremmou@citrix.com>
- Changed warning and info icon to match XenCenter's.
- Corrected label margins.
- Made list controls flat.
Signed-off-by: Konstantina Chremmou <konstantina.chremmou@citrix.com>
