You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Formerly "Self-extract HXE.exe to parent directory when 'Loader' state is inferred"
Expose HXE CLI functionality and features via either/both an embedded Terminal host and/or wrapped command-line command/arguments.
Terminal Host Embedded in GUI
The host would be embedded within an SPV3-themed GUI, similarly to our SPV3.Error UserControl.
PowerShell 7.2+ would be our preferred CLI host for its suggestions and completions, but most users will have PS 5.1 at best.
Embedding PowerShell 7.2 would bloat our application by at least 70MiB, so that's out of the question.
Check if PowerShell 7.2 is already installed on the client machine.
If not installed, prompt user with options: [ 'ignore once', 'ignore always', 'install for current user', 'install for all users' ]
A portable install is not presented because PowerShell itself is not portable. Also, that would be PITA to maintain without a package manager.
Wrapped CLI Commands and Arguments
Invoking SPV3 with HXE arguments will cause cause SPV3 Loader to pass unsupported arguments to the embedded HXE assembly which will then react appropriately, whether that be by throwing NotSupportException or acting upon the recognized argument(s).
The text was updated successfully, but these errors were encountered:
Expose HXE CLI functionality and features via either/both an embedded Terminal host and/or wrapped command-line command/arguments.
Terminal Host Embedded in GUI
The host would be embedded within an SPV3-themed GUI, similarly to our SPV3.Error UserControl.
PowerShell 7.2+ would be our preferred CLI host for its suggestions and completions, but most users will have PS 5.1 at best.
Wrapped CLI Commands and Arguments
Invoking SPV3 with HXE arguments will cause cause SPV3 Loader to pass unsupported arguments to the embedded HXE assembly which will then react appropriately, whether that be by throwing NotSupportException or acting upon the recognized argument(s).
The text was updated successfully, but these errors were encountered: