Script modules vs binary modules in PowerShell - Visual Side-by-Side Comparison

Concept Flow - Script modules vs binary modules

Start

↓

Choose Module Type

↓

Script Module

↓

Contains .psm1

↓

Load Functions

↓

Use in Session

↓

End

This flow shows choosing between script and binary modules, loading their contents, and using them in a PowerShell session.

Execution Sample

PowerShell

Import-Module MyScriptModule.psm1
Import-Module MyBinaryModule.dll
Get-Command -Module MyScriptModule
Get-Command -Module MyBinaryModule

This code imports a script module and a binary module, then lists commands available in each.

Execution Table

Step	Action	Module Type	Result	Output
1	Import-Module MyScriptModule.psm1	Script Module	Loads .psm1 file	Functions from script module available
2	Import-Module MyBinaryModule.dll	Binary Module	Loads .dll assembly	Cmdlets/functions from binary module available
3	Get-Command -Module MyScriptModule	Script Module	Lists commands	Shows script functions
4	Get-Command -Module MyBinaryModule	Binary Module	Lists commands	Shows binary cmdlets/functions
5	End	-	-	Modules ready to use in session

💡 Both modules loaded and commands listed, ready for use.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
$ScriptModuleCommands	null	Loaded functions	Loaded functions	Listed functions	Listed functions	Listed functions
$BinaryModuleCommands	null	null	Loaded cmdlets/functions	Loaded cmdlets/functions	Listed cmdlets/functions	Listed cmdlets/functions

Key Moments - 2 Insights

Why does importing a script module load a .psm1 file but a binary module loads a .dll file?

Script modules are plain PowerShell scripts saved as .psm1 files, while binary modules are compiled .NET assemblies saved as .dll files. This difference is shown in steps 1 and 2 of the execution_table.

Can both script and binary modules provide functions to use in PowerShell?

Yes, script modules provide functions written in PowerShell scripts, and binary modules provide cmdlets or functions compiled in .NET. This is clear from the outputs in steps 3 and 4.

Visual Quiz - 3 Questions

Look at the execution table, what file type does the script module load at step 1?

A .psm1

B .dll

C .exe

D .ps1

💡 Hint

Check the 'Result' column in step 1 of the execution_table.

At which step do we see the binary module commands listed?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Output' column for binary module commands in the execution_table.

If you only import the script module, what will $BinaryModuleCommands contain after step 2?

A Loaded cmdlets/functions

B null

C Listed cmdlets/functions

D Error

💡 Hint

Refer to variable_tracker row for $BinaryModuleCommands after step 2.

Concept Snapshot

Script modules are PowerShell scripts (.psm1) that define functions.
Binary modules are compiled .NET assemblies (.dll) providing cmdlets.
Import-Module loads these modules into your session.
Use Get-Command -Module to list available commands.
Script modules are easy to edit; binary modules offer compiled performance.

Full Transcript

This visual execution compares script modules and binary modules in PowerShell. Script modules are files with .psm1 extension containing PowerShell functions. Binary modules are compiled .dll files containing cmdlets or functions built with .NET. When you import a script module, PowerShell loads the .psm1 file and makes its functions available. When you import a binary module, PowerShell loads the .dll assembly and makes its cmdlets/functions available. You can list commands from each module using Get-Command -Module. Variables track the loaded commands after each step. Key moments clarify why file types differ and confirm both module types provide usable commands. The quiz tests understanding of file types, steps when commands appear, and variable states. The snapshot summarizes the key differences and usage tips.

Practice

1. Which statement best describes a PowerShell script module?

easy

A. It is a plain text file containing PowerShell functions and scripts.

B. It is a compiled DLL containing .NET cmdlets.

C. It requires Visual Studio to run.

D. It cannot be imported into a PowerShell session.

Solution

1. Step 1: Understand what a script module is

   A script module is a .psm1 file that contains PowerShell code in plain text format.

2. Step 2: Compare with other module types

   Binary modules are compiled DLLs, not plain text files, so they differ from script modules.

3. Final Answer:

   It is a plain text file containing PowerShell functions and scripts. -> Option A

4. Quick Check:

   Script module = plain text PowerShell code [OK]

Hint: Script modules are plain text files, binary are DLLs [OK]

Common Mistakes:

• Confusing script modules with binary DLL modules
• Thinking script modules require compilation
• Assuming script modules cannot be imported

2. Which of the following is the correct way to import a script module named MyModule.psm1 in PowerShell?

easy

A. Import-Module MyModule.psm1

B. Import-Module MyModule.dll

C. Load-Module MyModule.psm1

D. Add-Module MyModule.psm1

Solution

1. Step 1: Identify the correct cmdlet for importing modules

   PowerShell uses Import-Module to load both script and binary modules.

2. Step 2: Match the file extension with the module type

   Script modules use .psm1 extension, so Import-Module MyModule.psm1 is correct syntax.

3. Final Answer:

   Import-Module MyModule.psm1 -> Option A

4. Quick Check:

   Import-Module + .psm1 file = correct [OK]

Hint: Use Import-Module with .psm1 for script modules [OK]

Common Mistakes:

• Using Load-Module or Add-Module which don't exist
• Trying to import .dll as script module
• Omitting Import-Module cmdlet

3. Given the following PowerShell code, what will be the output?

Import-Module .\MyBinaryModule.dll
Get-Command -Module MyBinaryModule

medium

A. Lists all functions defined in the script module MyBinaryModule.psm1.

B. Throws an error because binary modules cannot be imported.

C. Lists all cmdlets exported by the binary module MyBinaryModule.

D. No output because Get-Command does not work with modules.

Solution

1. Step 1: Understand Import-Module with a DLL

   Importing a DLL file loads a binary module containing compiled cmdlets.

2. Step 2: Get-Command with -Module parameter

   Get-Command lists all commands exported by the specified module, here the binary module.

3. Final Answer:

   Lists all cmdlets exported by the binary module MyBinaryModule. -> Option C

4. Quick Check:

   Import DLL + Get-Command -Module = list cmdlets [OK]

Hint: Get-Command -Module lists commands from imported modules [OK]

Common Mistakes:

• Thinking binary modules cannot be imported
• Confusing script and binary module outputs
• Assuming Get-Command does not work with modules

4. You try to import a binary module using Import-Module MyModule.psm1 but get an error. What is the likely cause?

medium

A. Binary modules cannot be imported in PowerShell.

B. The module file is missing the .dll extension.

C. You must use Load-Module for binary modules.

D. The file extension .psm1 is for script modules, not binary modules.

Solution

1. Step 1: Recognize file extensions for module types

   Script modules use .psm1, binary modules use .dll files.

2. Step 2: Understand import errors

   Trying to import a binary module with a .psm1 extension causes errors because the file type is wrong.

3. Final Answer:

   The file extension .psm1 is for script modules, not binary modules. -> Option D

4. Quick Check:

   Wrong extension causes import error [OK]

Hint: Binary modules use .dll, script modules use .psm1 [OK]

Common Mistakes:

• Assuming binary modules can't be imported
• Using Load-Module instead of Import-Module
• Ignoring file extension importance

5. You want to create a PowerShell module that runs fast and includes advanced .NET features. Which module type should you choose and why?

hard

A. Script module, because it is easier to write and maintain.

B. Binary module, because it is compiled and supports advanced .NET features.

C. Script module, because it loads faster than binary modules.

D. Binary module, because script modules cannot be imported.

Solution

1. Step 1: Identify module types and their strengths

   Script modules are plain text and easy to write but slower and limited in features.

2. Step 2: Match requirements with module type

   Binary modules are compiled DLLs, run faster, and can use advanced .NET features.

3. Final Answer:

   Binary module, because it is compiled and supports advanced .NET features. -> Option B

4. Quick Check:

   Performance + advanced features = binary module [OK]

Hint: Use binary modules for speed and .NET features [OK]

Common Mistakes:

• Choosing script modules for performance needs
• Thinking script modules load faster
• Believing binary modules cannot be imported