Any packaged exe will instantiate the currently installed PowerShell version. As there is only ONE officially installed PowerShell version, that is expected.
You should always package for the version installed on a system. As you can see from the error, the package does not actually work on a system that is not matching the packaged version.
That is because .NET does not allow 'upscaling' versions, so assembly reference to lower versions cannot use a newer version of an assembly. That is inherent to .NET past the
.NET framework Windows PowerShell uses.
Because that is an issue for deploying packages in environments that are not homogenous, we are providing "PowerShell runtimes" which can be rolled to have a fixed version reference.
The runtimes can be downloaded from the "PowerShell 7 runtimes" link in the SAPIEN Script Packager ribbon. You can also find them on your SAPIEN account page.
A packaged executable will reference the assemblies of the matching runtime (if installed) rather than those of the installed Powershell version.
As a side note, if a runtime is installed, an officially installed PowerShell 7 version is normally no longer required, unless specific code within the packaged application references that..
You should always package for the version installed on a system. As you can see from the error, the package does not actually work on a system that is not matching the packaged version.
That is because .NET does not allow 'upscaling' versions, so assembly reference to lower versions cannot use a newer version of an assembly. That is inherent to .NET past the
.NET framework Windows PowerShell uses.
Because that is an issue for deploying packages in environments that are not homogenous, we are providing "PowerShell runtimes" which can be rolled to have a fixed version reference.
The runtimes can be downloaded from the "PowerShell 7 runtimes" link in the SAPIEN Script Packager ribbon. You can also find them on your SAPIEN account page.
A packaged executable will reference the assemblies of the matching runtime (if installed) rather than those of the installed Powershell version.
As a side note, if a runtime is installed, an officially installed PowerShell 7 version is normally no longer required, unless specific code within the packaged application references that..
Statistics: Posted by Alexander Riedel — Thu Jun 27, 2024 9:53 am