Patrick Meinecke

So for that module, it needs to create the runspace on module load. There isn't really a way for that module to know you didn't *actually* want to import it....

> Moreover, the current version of PowerShell runtime already uses exactly this behavior: FYI the test would be `[System.Runtime.CompilerServices.RuntimeFeature]::IsSupported('NumericIntPtr')`, what you have there just returns a string regardless of configuration....

Direct type name comparisons may not be necessary depending on the result of dotnet/runtime#43638

@SteveL-MSFT The issue has existed since version 3 (as noted by @mklement0 above) and happens with any command (e.g. `$i = '10'; echo $i..HEAD`). @IISResetMe mentioned on twitter that it...

> Given that a native executable happened to be the messenger, if you will, in this case, perhaps @SteveL-MSFT merely meant to showcase the new-in-preview.5 ability to also trace parameter...

> That however needs, from my understanding changes in dotnet to achieve. I believe it would need changes to how file systems are structured in general. --- For `Start-Transcript` specifically...

@theJasonHelmick I'm pretty certain you're right and that's what they're asking for. A build in argument completer for it would be great, I always found it strange that there wasn't...

> Would it be OK to add a reference to System.CommandLine? Any reference we add essentially version locks that library for anyone else who wants to consume it. There's a...

The Interactive WG discussed the issue regarding multiple catch all completers today. For the first iteration of this we think it's best to keep to a single registered completer due...

So the intellisense provided by PSES is powered by the same API that powers tab completion in the PowerShell engine. For a lot of things, that API relies on session...