Strange text behaviour

[brittneyr]

We are currently investigating this behavior. In the meantime, it is generally not good practice to have function names in scripts that match the names of functions in modules as there is no namespaces in PowerShell that separates the two.

[Lembasts]

It would be lovely if my Powershell Studio could just call functions that were in my module and not have a separate 'commonfunctions' script in my project.
If I called functions from my module would I require that the module be present wherever the PS compiled exe is run? Or would it just drag the code in at compile time so I only need the module on the computer where I build my package?

[Alexander Riedel]

Powershell Studio does not determine which function is called if there is a name collision. Windows PowerShell does.
The mechanism employed by PowerShell is documented here: https://docs.microsoft.com/en-us/powers ... wershell-7
You can use a module qualified name (See https://www.sapien.com/blog/2015/10/23/ ... let-names/) to specifically point to the exact function in a module.
The mechanism exists to allow for resolving conflicts between modules which use identical cmdlet names. But obviously it also allows for avoiding a name collision with a local function.

To your last question, a PowerShell module is, akin to a dll, intended to share functionality between multiple applications. That includes application that are created by someone else. As such it would not make much sense to "drag the code in" and thereby make it private to the application. It would in essence defeat the very purpose of a module.

If you want to share common functions between your and ONLY your applications, you would dot source a script containing such functions. And yes, our script packager does have the ability to resolve dot sourced files by including its content in lieu of the dot source statement.

[Alexander Riedel]

I want to add here, that PowerShell will not automatically load your module as it typically would if there is a name collision.
Under normal circumstances, if you call Get-Lembasts, PowerShell will find a module that has that cmdlet, load it and call the cmdlet.
If however you already have a function called 'Get-Lembasts' in your script, PowerShell has no reason to find a module for it.
So your module will not be loaded at all, unless you specifically call 'Import-Module'

[Lembasts]

Thanks - My module is a psm1 file with just powershell text.
Basically I have a bunch of scheduled scripts which use the psm1 module and I have a commonfunctions.ps1 file which is part of all my powershell studio projects. Both the scheduled scripts and PS projects do similar things - hence the duplicate names. For example they both have an 'Open-SQLDatabase' function. The computer I run my P-Studio on also has the module in the standard posh module folder. Its only recently that Ive seen this weird text behaviour. Unless I can use one file to store common functions for both PS Studio and scheduled scripts then Ill just have to make sure there are no duplicate names.