saica1101
commented
6 months ago I understand the cause now. First, it was because the necessary DLL was set to block access from external sources. After allowing access from the properties of each DLL, the "DLL load error" no longer occurred. However, the next issue arose when loading the XAML. This seems to occur with PowerShell 5.x, so I used iExpress and compiled it with PowerShell 7.x, which allowed it to start without any issues. "powershell.exe -ExecutionPolicy ByPass script.ps1" -> Does not work "pwsh.exe -ExecutionPolicy ByPass script.ps1" -> Works
So, here's my question: I'm currently compiling with PowerShell 5.x, but in the future, will I compile with PowerShell Core (7.x)? If possible, it would be great to have the option to choose whether to compile with 5.x or 7.x.
MScholtes
Hello, First of all, thank you for developing this wonderful tool.
I used PS2EXE, but it couldn't load the required DLLs. Why is this happening?
The error message is in Japanese, so I translated it as follows: Error: An exception occurred while calling the "LoadFrom" with "1" argument(s): "File or assembly" omitted or one of its dependencies could not be loaded. Operation is not supported. (Exception from HRESULT: 0x80131515)"
The relevant script is as follows: `$AssemblyLocation = Join-Path -Path $ScriptPath -ChildPath assembly foreach ($Assembly in (Get-ChildItem $AssemblyLocation -Filter *.dll)) {
Write-Host $Assembly` }