4 ms·

Thanks this is very clear. I use COM objects through PowerShell too, not the Import-Excel module, because I cannot install anything (except Office) on my client

Thanks this is very clear. I use COM objects through PowerShell too, not the Import-Excel module, because I cannot install anything (except Office) on my client's work machine. But I can copy binaries so working with Lua might relieve my headaches from working with PowerShell :)

jodrellblank 2y ago
From the PowerShell Github releases page[1] you can expand 'assets' and 'show more assets' and find a ZIP distribution which doesn't need installing, unzip it. e.g. PowerShell-7.4.2-win-x64.zip . Then from PowerShell 7 somewhere, run Save-Module ImportExcel -Path C:\Whatever\ and copy that module folder along with the PowerShell folder to the remote machine, and you can import modules from a full path: Import-Module C:\Whatever\ImportExcel and do a no-install copy-paste deployment of powershell 7 and modules. (I'm not saying you should do this instead of using Lua, just that you can). [1] https://github.com/PowerShell/PowerShell/releases https://github.com/PowerShell/PowerShell/releases
- bionsystem 2y ago
  Nice, thanks. But I have other limitations as well (Powershell 5 only and scripts must be signed, which I believe includes external modules). Don't ask me why I can run a random binary instead, I don't know and I don't want to know.