Roman Kuzmin

As a result, the command like `Select-EverythingString Search-Everything -CaseSensitiveSearch` fails with ``` Select-EverythingString : A parameter cannot be found that matches parameter name 'CaseSenitive'. At line:1 char:1 + Select-EverythingString Search-Everything...

NB In the PR I'd also tweak these: - seemingly unused file/class https://github.com/powercode/PSEverything/blob/master/PSEverythingStandard/Class1.cs - the `PowerShellStandard.Library` package may be updated from preview to release

Here is the typical gotcha: - My aliases are set in the profile for interactive sessions - Then I invoke `Search-Everything` in a session - `PSEverything` is auto imported and...

So the suggested workarounds are unfortunately not very handy > will only import the functions Then I have to remember typing this command and remember not to trigger auto loading...

It sounds good. I'll create a new command similar to *New-VSCodeTask.ps1*.

This would be useful to know: - How is a registered command invoked internally? By *powershell.exe* or in the current session? In the terminal or integrated console? - Is there...

Added the script *Register-VSCodeTask.ps1*. For now, it is available in the repository and [PSGallery](https://www.powershellgallery.com/packages/Register-VSCodeTask).

@daviwil How is it going?

@Jaykul > Why is everyone trying to create these non-deterministic "task" systems? What do you see as the payoff, versus a simple, linear build script? I tried to answer this...

@Jaykul Tasks have "inputs" and "outputs", see Invoke-Build wiki - [Incremental-Tasks](https://github.com/nightroman/Invoke-Build/wiki/Incremental-Tasks) - [Partial-Incremental-Tasks](https://github.com/nightroman/Invoke-Build/wiki/Partial-Incremental-Tasks)