At the time that this post was written, PowerShell was only available in version 1 which is why I came up with this solution. In version 2, the module feature was added to PowerShell. Modules can be loaded/unloaded on demand using Import-Module and Remove-Module, allowing you to load libraries of functions without worrying about whether or not you dot-source them or invoke them directly. This is the feature you are looking for.

As for examples, I recommend the following:

1. Download and install PowerGUI (you can find that here: http://www.powergui.org).
2. Download and install the Module Management Add-on for PowerGUI (you can find that here: http://powergui.org/entry.jspa?externalID=2983&categoryID=21).
3. In the PowerGUI Script Editor, select File | New | Module to create a new module. This will give you the framework for your module.
4. Now add your functions to your module by putting them in your psm1 file or by dot-sourcing files containing functions.
5. Save your files and load your module.

If you follow these steps, you’ll have a module that you can load and unload on demand. All functions inside a module are public by default. If you want private functions, have a look at the PowerShell v2 snippets in PowerGUI (Edit | Insert Snippet, then open the PowerShell v2 container to see the snippets). There are snippets allowing you to insert whatever type of function you want into your module.

Another alternative for module creation would be to open a script file where you have functions defined and then use the File | Convert to Module menu item (this is also part of the Module Management Add-on). That will give you a module that automatically contains the functions defined in your script file.

Don’t hesitate to come back with more questions if you have any.

Kirk out.

What about modular option? doesn’t powershell support somthing simalar to python modules…if so do you know where to find some examples?

thanks

chagrinedly,
kent

The difference in execution can be seen when you compare dot-sourcing the script to invoking the script using the call operator.

For example, if you created a Test-Invoke.ps1 script file, compare this:

# Note you must include the leading dot to dot-source the file contents
. .\Test-Invoke.ps1

to this:

# In this case the call operator is actually not necessary, I just include it for completeness.
& .\Test-Invoke.ps1

In your comment it seems like you were comparing the same thing: using the call operator and invoking the script using the relative path.

Let me know if you get different results by using dot-sourcing.

Thanks,

Kirk out.

Name is required
At C:\Users\kentd\test-invoke.ps1:4 char:32
+ param ([string]$name = $(throw <<<< 'Name is required') )
+ CategoryInfo : OperationStopped: (Name is required:String) [], RuntimeException
+ FullyQualifiedErrorId : Name is required

As you can see, I am a bit confused….Can you help?

thanks
kent