initial commit of module

[TylerLeonhardt]

It supports:

Push-OutputBinding -Name foo -Value bar
Push-OutputBinding -InputObject @{ foo = bar; baz = 5 }
@{ foo = bar; baz = 5 } | Push-OutputBinding

# and 

Get-OutputBinding
Get-OutputBinding -Name foo
Get-OutputBinding -Name f*

I'll hook it up in a separate PR.

[TylerLeonhardt]

@daxian-dbw I moved the module into the Worker project so that we can have dotnet build and publish put the module in the bin directory. This will be easier for packaging. Let me know what you think.

[daxian-dbw]

$dict here seems unnecessary to me. For NameValue set, you can just check for the existence of the key in $script:dict; for inputobject set, you can directly process the in-coming Hashtable.

[TylerLeonhardt]

I didn't want to have 2 if/else's. I usually prefer to have a switch statement define values and then have logic at the bottom work for all cases.

That said.. I made the change.

[daxian-dbw]

I don't like the code duplication too, that can be addressed by define a non-exposed function in the module. The problem was in $dict = @{} in the process block. That means for each pipeline input, you are creating a dictionary.

Another way to tackle it is to define $dict = @{} in the begin process, and use the same dictionary throughout the life cycle of the cmdlet. But I guess a common use of this cmdlet would be just simply Push-OutputBinding -Name blah -Value value. Always having a dictionary created for that is not very efficient.

[daxian-dbw]

Per our discussion offline, let's remove the unused entries in the psd1.

[TylerLeonhardt]

Thanks @daxian-dbw!