How to Source all powershell scripts from a directory

Question

Can not dot source all PowerShell scripts from directory tried:

. .\*.ps1

Returns this:

>  : The term '.\*.ps1' is not recognized as the name of a cmdlet,
> function, script file, or operable program. Check the spelling of the
> name, or if a path was included, verify that the path is correct and
> try again. At line:1 char:3
> + . .\*.ps1
> +   ~~~~~~~
>     + CategoryInfo          : ObjectNotFound: (.\*.ps1:String) [], CommandNotFoundException
>     + FullyQualifiedErrorId : CommandNotFoundException

I wish . .\*.ps1 worked

Kellen Stuart
– Kellen Stuart

2017-11-07 17:22:58 +00:00
Commented Nov 7, 2017 at 17:22 — Kellen Stuart
– Kellen Stuart, Commented Nov 7, 2017 at 17:22

jcolebrand · Accepted Answer · 2018-06-25 20:05:17Z

13

Use Get-ChildItem to grab all *.ps1 files, then loop through them with ForEach-Object and dot-source them individually

$Path = "C:\Scripts\Directory"
Get-ChildItem -Path $Path -Filter *.ps1 |ForEach-Object {
    . $_.FullName
}

If you put the above in a script, and the script itself is located in $Path, make sure to exclude the file itself so as to avoid it recursively dot-sourcing itself over and over again:

$Path = "C:\Scripts\Directory"
Get-ChildItem -Path $Path -Filter *.ps1 |Where-Object { $_.FullName -ne $PSCommandPath } |ForEach-Object {
    . $_.FullName
}

Edit: jcolebrand - 2018-06-25

Used the above to define a folder called Functions under my executing script. Works just fine in PS5:

## Folder\myIncluder.ps1
## Folder\Functions\Some-Function.ps1          -included
## Folder\Functions\Some-Other-Function.ps1    -included
## Folder\Functions\Some-Other-Function.readme -not included
(Get-ChildItem -Path (Join-Path $PSScriptRoot Functions) -Filter *.ps1 -Recurse) | % {
    . $_.FullName
}

Figure this makes it easy for the next lazy person to just adopt the same structure :p

edited Jun 25, 2018 at 20:05

jcolebrand

16k12 gold badges78 silver badges123 bronze badges

answered Jul 19, 2016 at 22:06

Mathias R. Jessen

178k13 gold badges175 silver badges234 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Alex Over a year ago

If I add this command to a file, source it and execute, it hangs. By any chance, do you know how can I put this command in file such that it works?

Mathias R. Jessen Over a year ago

That's because it recursively starts dot-sourcing itself, that can be fixed though, let me update the answer

Martin Brandl · Accepted Answer · 2016-07-19 22:06:12Z

3

This should work:

Get-ChildItem -Filter '*.ps1' | Foreach { . $_.FullName }

answered Jul 19, 2016 at 22:06

Martin Brandl

59.4k16 gold badges151 silver badges190 bronze badges

Comments

AP. · Accepted Answer · 2017-11-07 18:55:57Z

0

To achieve this, you can loop through all your PowerShell files, and source them:

foreach ($ps1 in (ls *.ps1)) {
    . $ps1.FullName
}

edited Nov 7, 2017 at 18:55

AP.

9,0112 gold badges28 silver badges36 bronze badges

answered Nov 7, 2017 at 17:24

Kellen Stuart

9,0919 gold badges72 silver badges88 bronze badges

Collectives™ on Stack Overflow

How to Source all powershell scripts from a directory

3 Answers 3

2 Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related