237dmitry

I tried and no errors. ArcoLinux, pwsh 7.2.1

Because `using` is the .Net statement and it does not know about powershell's aliases or variables.

`~` is powershell (and other unix shells) alias for the user home directory. It does not exist in file system. ```powershell PS > $a = [io.directoryinfo]::new('~') PS > $a.Exists False...

Try to use `using namespace` to define namespace + Add-Type cmdlet to load module. ``` using namespace Module.Namespace Add-Type -assembly "~/path/to/module.dll" ``` 

> and even if it were, somewhere between the PowerShell parser and the .net internals the path should be resolved. .Net syntax is not friendly with ` ~ ` as...

> I need to import the classes out of the psm1 You can place module in `$env:PSModulePath`. After that you will be able to load the module by name ```...

> I don't see why ~ shouldn't also work. From help `about_using`: > When \ is a path, the path can be fully qualified or relative. Full path. Literally.

> module names should be case insensitive. This is not Windows. Script names are also case sensitive.

I think this is not matter as `$null ? $true : $false` returns `False` Another thing is that the documentation states that if there is a mismatch `False` should be...

In my opinion, this is unnecessary. This will complicate the cmdlet. This functionality is very easy to replace with `-notmatch` and `-notlike` operators. For example: ``` (Get-Childitem -Recurse ./.local) -notlike...