PowerShell-Guru "Don’t do that #11: Reload a module with Remove-Module and Import-Module".
- To reload a just-edited PowerShell module under development, do “Import-Module -Name module -Force - Verbose”.
StackOverflow "How to import splitpipeline module from a shared server?".
- The issue you're experiencing is that .NET assemblies can't be loaded from an untrusted UNC path, without special configuration. As you already discovered, the simplest solution is to copy the module to your local computer first.
- To work around the “Access Denied” message, copy the module to your user directory “C:\users\Administrator\Documents\WindowsPowerShell\Modules” ( with <user> = “Administrator”), not the system-wide directory.
How to work with local PowerShell repositories:
- Register-PSRepository -SourceLocation \\computername\\path - Name repo
- Install-Module - Name MyModule -Repository repo

DLL Development

Load a Custom DLL from PowerShell

[Reflection.Assembly]::LoadFile
- Lee Holmes, Precision Computing. Software Design and Development "Load a Custom DLL from PowerShell" - '[Reflection.Assembly]::LoadFile(“c:\temp\MyMathLib.dll”)'.
- Microsoft MSDN Developer Network "<loadFromRemoteSources> Element".
- Error message when trying to load a DLL by '[Reflection.Assembly]::LoadFile(“c:\temp\MyMathLib.dll”)': “Exception calling “LoadFile” with “1” argument(s): “An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See Microsoft MSDN Developer Network "<loadFromRemoteSources> Element" for more information.”

Resources

PowerShellMagazine "Writing a PowerShell module in C#, Part 1: The basics".
PowerShellMagazine "Basics of Writing a PowerShell Module with C#, Part 2: Debugging".
PowerShellMagazine "The Windows PowerShell 3.0" - 'Note that in order to use the samples you’ll need to install the Microsoft MSDN "Windows Software Development Kit (SDK) for Windows 8" which includes the reference assemblies for Windows PowerShell 3.0'.
Code Project "Custom CSharp Control for Powershell" - “IMPORTANT: You must set the correct powershell execution policy *AND* you will have to unblock the PSMap.dll file ( C:\PSMapDll-Deploy\PSMap.dll – Click on Properties → Unblock )”.

Development of Windows Services by Windows PowerShell

Development of Windows Services by Windows PowerShell, with little help by the "Windows Server 2003 Resource Kit Tools" srvany.exe and instsrv.exe

Microsoft Download Center "Windows Server 2003 Resource Kit Tools".
- This toolkit also contains Robocopy, before it was included in the Win2008 Server distribution.
- Microsoft Support "How to Create a User-Defined Service".
- Windows Server How-To Guides "Applikationen als Dienste einrichten".

Development of Windows Services by Windows PowerShell and C#

Microsoft
GitHub "PSUGH / PowerShell/20-10-2017 PowerShellWindowsDienst/"# - “Einen Windows-Dienst mit PowerShell erstellen”.
Falls mal jemand fragt. IT-Blog und auch total anderes Zeug "Einen Windows-Dienst mit Powershell anlegen".
Windows-FAQ "PowerShell – Dienste auflisten, stoppen und starten".
Windows Services are similar to Linux's Cron & Systemd services .

Tools, Frameworks, Technologies

BloodHound

GitHub "BloodHoundAD/BloodHound" - “BloodHound is a single page Javascript web application, built on top of Linkurious, compiled with Electron, with a Neo4j database fed by a PowerShell ingestor. BloodHound uses graph theory to reveal the hidden and often unintended relationships within an Active Directory environment”.

Desired State Configuration ( DSC ) of Windows

See Device Description Languages and Device Parameterization.

Psake - Build Manager

GitHub "psake/psake".
EN.Wikipedia "Psake" - “A domain-specific language and build automation tool written in PowerShell to create builds using a dependency pattern similar to Rake or MSBuild. It dramatically simplifies the build language as compared to MSBuild scripting”.

Generation of PowerShell GUI Applications with WPF

The discontinued PowerBoots

Archive.org "powerboots.codeplex.com".
- “PowerShell PowerBoots” ( - 2010-12-24 )
- “Show-UI: The PowerShell WPF Toolkit” ( - 2011-03-08 ).
Software Developer: Joel 'Jaykul' Bennett - Huddled Masses.
- Archive.org "Huddled Masses "PowerBoots: The tutorial walkthrough" ( - 2012-01-10 ).

ShowUI, the Successor of PowerBoot

CodePlex "ShowUI: Write-UI -in PowerShell"
Software Developer:
- Start-Automating - “A software services company”.
- Joel 'Jaykul' Bennett - Huddled Masses.
YouTube Channel "StartAutomating".
- “ShowUI. Videos to get you started with ShowU”
  1. YouTube "Getting Started with ShowUI".
    - Open ISE, execute “Import-Module ShowUI”.
  2. YouTube "Getting Started with ShowUI - Get-Input by StartAutomating".
  3. YouTube "Writing Controls in ShowUI: Show-CPU by StartAutomating".
  4. YouTube "Show-Clock - Writing a Complete ShowUI function".

Resources

Windows PowerShell Blog. Automating the world one-liner at a time "PowerBoots 0.2 is Now Available".
Will - Another computer blog. A spot to record my explorations in Windows. Focused lately on PowerShell "PowerShell - ShowUI: Walkthrough".
“ShowUI is the next generation PowerShell module for building user interfaces in script. It’s the merger of my previous PowerShell UI project (called PowerBoots) with one by James Brundage, former Microsoft PowerShell team member and founder of Start-Automating (called WPK) which shipped in the Windows 7 resource kit”.
PauerSchell Blog "WPF Linkcollection for PowerShell".
StackOverflow "Can you implement Model-View-ViewModel using Powershell and WPF using PowerBoots?".

Package Manager & Repositories

There are
1. Package repositories ( in the Clowd ).
2. Package provider.
3. Package manager ( on the local PC, do almost nothing, at least not “packaging” ).

Galleries / Repositories

Chocolatey

Chocolatey.
- Chocolatey - Search for "Pester".
- Twitter "Chocolatey NuGet, @chocolateynuget".
BoxStarter, GitHub "mwrock/boxstarter", CodePlex "BoxStarter" - “Repeatable, reboot resilient windows environment installations made easy using Chocolatey packages”.

NuGet

NuGet.
NuGet Docs.
- NuGet Docs "Command Line Reference".
- NuGet Docs "Installing and Updating NuGet Client".
  - “For Visual Studio 2010, NuGet is available through the Visual Studio Extension Manager... Additionally, the extension can be installed into Visual Web Developer 2010 Express”.
  - “Starting with Visual Studio 2012, NuGet is included in every edition (except Team Foundation Server) by default. Updates to NuGet can be found through the Extension Manager”.
  - “To check if your copy of Visual Studio already has the NuGet extension, look for Library Package Manager in the Tools menu of Visual Studio. If your copy of Visual Studio does not already have the Library Package Manager (NuGet) extension, you can install it using the Extension Manager”.
- NuGet Docs "Finding and Installing a NuGet Package Using the Package Manager Console".
Blog NuGet Team Blog.

OneGet & PowerShellGet

PSGet

PSGet, GitHub "psget".
- Alternatively you can do installation manually:
  1. Download PsGet.psm1 from http://www.github.com/psget/psget/.
  2. Copy PsGet.psm1 to your modules folder ( e.g. Modules\PsGet\ ).
  3. Execute Import-Module PsGet (or add this to your profile).

Frameworks by Friedrich "Fred" Weinmann

PowerShell Framework - “The project dedicated to empowering your PowerShell scripting”.
Active Directory Management Framework - “Configuration driven Active Directory management.”.

Just Enough Admin ( JEA )

Windows PowerShell Tips & Tricks

Best training strategy, according to PowerShell experts:
1. First learn how to use PowerShell for Windows system administration.
2. Afterwards, you may also learn how to use PowerShell as a Window developer.
Run “start /w aCommand” to get the script prompt back after the execution of the command “aCommand” is finished. Else the prompt returns immediately and the shell does not wait for completion of the execution of “aCommand”.
The most important commands for rookies:
1. PowerShell command “get-command”.
2. PowerShell command “get-help”.
3. Application “powershell_ise.exe”.
4. Since PowerShell 3, help must be installed manually, by “Update-Help -force -verbose UIculture de-DE”, Update-Help -UICulture 'en-US'.
There are 2 levels of compatibility


Version	.NET	Compatibility	Operating System	Comments
Powershell 1	.NET 2.0	1 & 2	WinXP	outdated
Powershell 2	.NET 2.0, .NET 3.5	1 & 2	WinXP	supported
Powershell 3	.NET 4.0, .NET 4.5	3 & 4	Win7, Win8	supported
Powershell 4	.NET 4.0, .NET 4.5		Win7, Win8.1	supported, can't be installed on Win8
Powershell 5	?		Win7, Win2012, Win8.1, Win10	supported

Redirection:
- In opposite to the Linux / Unix shells, e.g. Bourne Shell, there is no input redirection, even with “Powershell 5” .
- Full output redirection was a lately implemented feature of Powershell .
- Remember that with output redirection, not plain text, but objects are returned - that's much more than available with Bourne Shell or other text-based input redirection.
- How to redirect StdErr with PowerShell: “application.exe 2>&1 >saved_stderr.txt”.
Stack Overflow "How to start PowerShell from Windows Explorer?" - “In Windows Explorer, just go to the Address Bar at the top (keyboard shortcut: Alt+D) and type powershell and press Enter. A PowerShell command window opens with the current directory”.
If you don´t own Win8.1 or Win2012Server, you don´t get the latests high-level functions. On Win7 and Win2008Server, if you want do implement the missing high-level functions by your own, you have to write .NET software in C#.
- Unfortunately, the names of methods you need are not mentioned in the PowerShell documentation. Instead, you have to find it in the .NET and WPL documentation, by yourself!
- It is challenging to get names of methods you want to use, by the .NET and WPL documentation.
PowerShell Execution Policies.
- Microsoft TechNet "about_Execution_Policies".
- I myself like to create and use a batch file “powershell_unrestricted.ps1” with the contents “PowerShell.exe -ExecutionPolicy Unrestricted” to work without restrictions.
StackOverflow "Determine installed PowerShell version" - “$PSVersionTable.PSVersion”.
File location:
- Modules:
  - Powerscript modules are located in subdirectories of the Windows directory “C:\Windows\System32\WindowsPowerShell\v1.0\Modules”.
  - You may open your modules directory with PowerShell by “explorer.exe ($PSHOME | Join-Path -ChildPath Modules)”.
- Autoexec files ( e.g. <user> = “Administrator” ). If you refer to other files in the directory, you have to specify the full absolute path to it!
  - “C:\Users\Administrator\Documents\WindowsPowerShell”.
    - “C:\Users\Administrator\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1”.
    - “C:\Users\Administrator\Documents\WindowsPowerShell\Microsoft.PowerShellISE_profile.ps1”.
SuperUser "Configure the Windows Powershell to display only the current folder name in the shell prompt".
Reset.
- With ISE → See on this page, at other location.
- With PowerGUI → See on this page, at other location.
- PowerShell Magazine "#PSTip Reset your ISE runspace"
- PowerShell Magazine "#PSTip Restarting PowerShell as an administrator".
How-To-Geek "How to Configure Windows to Work with PowerShell Scripts More Easily".
My experience with ISE “caching” of old files ( see StackOverflow "Windows PowerShell ISE running old version" ):
- The behaviour of ISE is different for PS modules ( .psm1 ) and simple PS scripts ( ps1 ). I am using PS&ISE with Win10Pro.
  - My experience with modules ( .PSM1 )
    1. Load a module file “hello.psm1” already placed in a proper module directory ( e.g. “C:\Users\MyUserName\Documents\WindowsPowerShell\Modules\Hello” ) by ISE.
    2. Execute a function by “Run Selection” ( you may not execute modules by “Run Script” ).
    3. Modify the file, e.g. the output of the function 'Write-Host “Hello World!”' to 'Write-Host “Hello”' and save the file.
    4. Execute a function by “Run selection”, and it will execute the old function, with old output, e.g. “Hello World!”. This is also true if I repeat the “Run Selection” command.
    5. Just if I leave ISE and load it again, the new function is executed by “Run Selection”.
  - My experience with scripts ( .PS1 ).
    1. If I execute “Run Selection”, the same behaviour as with modules.
    2. If I execute once “Run Script” and by that the function is called, the current version of the function is executed. Of course I call the function ( e.g. on line number 100 ) in the file “after” it is defined ( e.g. in lines 10-20 ). By this, there is no caching.
    3. Especially and consequently, if I execute once “Run Script”, while the executed code doesn't call the function, and then execute my function by “Run Selection”, the current version of the function is executed.
  - Here is my workaround to make module development more comfortable:
    - Simple scripts may be executed by “Run script”.
    - If I want to develop a module ( .PSM1 ), I name it as simple script ( .PS1 ) during the development phase. I place the file ( e.g. “hello.ps1” ) already in the proper module folder, e.g. “C:\Users\MyUserName\Documents\WindowsPowerShell\Modules\Hello” for a module “Hello”. Of course by this I can´t execute the functions as module functions from PowerShell console. I just want to use ISE to call functions for testing.
    - As modules are not executed as script, there is no executable code in the file, but just functions ( AFAIK ). So I may safely execute a “Run Script” on my script.
    - So if I modify a module file under ISE development, I always first execute “Run Script”, before I execute a function by “Run Selection”. By this I always execute the current version of a function.
How to get a static variable which is not reset by calling a new PS script:
- Function:
```
$a=1
$code={
    $scipt:a++
    $a
} GetNewClosure()
```
- Call: ”&$code”
- Output: 1234567