Additional details:
- Some (short) scripts are inline, but longer and more complex scripts are contained in separate files.
- The scripts should not be installed to the target system. They are only used during installation.
Thanks
Hans
This is indeed true. The module would have to be imported in the current PowerShell session.If I understand modules right, a module must exist as a disk file before it is used.
To overcome this, we could make use of temporary files.But in my situation, the script runs during the UI phase of the installer, so the installer hasn't copied anything to disk yet.
Temporary files could help here as well, since they are automatically removed at the end of the installation, unless told otherwise.Besides, I don't want the script and its modules to be left on the target system.
FOLLOW US
Get the latest news in Application Packaging