Patrick Meinecke

/cc @PaulHigin @daxian-dbw A possible "solution" is to try to block PowerShell classes from being carried over. Sort of like how script blocks currently work. If #4003 was *fixed*, this...

Just straight up recreating it is a little sketchy though because you'd lose state from static properties. Property accessors don't (currently) invoke any PowerShell so they aren't subject to the...

**NOTE**: The examples below should never be purposefully relied on, they are incredibly dangerous and can corrupt state in unexpected ways and/or cause general instability. > Isn't the current behavior...

Personally I think these behaviors would be the most ideal for method invocations. If called on: 1. The origin runspace thread - run with `SessionState` affinity like normal 1. A...

> With #3, is it more desirable to throw there, or take the time to spin up a runspace to execute in anyway, so as to "make" it work without...

Another consequence of this is that if you call a second method from the first one, you get a dead lock. ```powershell class Test { static [void] FirstMethod() { [Console]::WriteLine('First...

Thank you so much for gettin' the ball rollin' on this ❤️ > I planned to implement hover and highlight quickly, but highlight requires `FindReferencesVistor` also Just a heads up...

~~Related (but not dupe) #13674~~ Eh not really

We talked about this a little bit on discord: > seeminglyscience — Today at 10:55 AM honestly in that case, the error might be preferable over actually invoking the code...

> This seems too uncompromising a decision. If we go this way, we rather need an option. Then the main difficulty will be to decide whether it should be opt-in...