"(&mise activate pwsh) | Out-String | Invoke-Expression" inside the profile.ps1 throws MethodInvocationException

[luzede]

When the (&mise activate pwsh) | Out-String | Invoke-Expression is added to $PROFILE location profile, it does not throw an error and it works.

When it is added on profile.ps1 after running Edit-Profile to edit the profile that extends the $PROFILE it throws an error when new terminal session is started.

I was gonna post the issue on mise github page but when added on $PROFILE it was not giving error, or when running the command in the terminal. The tool is https://github.com/jdx/mise

[pnavais]

Workaround: place your custom logic in CTTcustom.ps1 in the same PowerShell profile folder as Microsoft.PowerShell_profile.ps1 ($PROFILE).
CTT loads that file near the end of the main profile, so it lets you run custom commands like mise without editing the hashed/upstream-managed profile.

In my case, adding (& mise activate pwsh) | Out-String | Invoke-Expression to CTTcustom.ps1 instead of profile.ps1 fixed the issue.

[luzede]

I got it working through CCTcustom.ps1 but I wanted everything in one file so I found a different workaround and appended it to profile.ps1:

Register-EngineEvent -SourceIdentifier PowerShell.OnIdle -MaxTriggerCount 1 -Action {
    (&mise activate pwsh) | Out-String | Invoke-Expression
}

Basically it triggers the event once, when PS profile fully loads.

It is an AI suggested solution and from my understanding it registers an event listeners that should only trigger once, when it receives OnIdle event.

If you don't want the print of event registration, use Out-Null:

Register-EngineEvent -SourceIdentifier PowerShell.OnIdle -MaxTriggerCount 1 -Action {
    (&mise activate pwsh) | Out-String | Invoke-Expression
} | Out-Null

[pnavais]

Bear in mind that using "PowerShell.OnIdle" is brittle and not deterministic , since is not a guarantee of knowing that all startup profiles have been loaded. CTTCustom.ps1 is the one intended to be loaded after CTT has been fully loaded, In the case of mise, the PSReadline customization done in CTT is interferring with the mise hooks loaded before and that is the reason we get the errors, so mise stuff needs to be loaded after CTT profile.If you use profile.ps1 you will always load your stuff before CTT, and "PowrShell.OnIdle" may fail.