<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>powershell on Luke In The Clouds</title>
    
    
    
    <link>https://lukeintheclouds.com/tags/powershell/</link>
    <description>Recent content in powershell on Luke In The Clouds</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 10 Nov 2025 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://lukeintheclouds.com/tags/powershell/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>The Import-Module trap: How PowerShell pros handle dependencies</title>
      <link>https://lukeintheclouds.com/posts/the-import-module-trap-how-powershell-pros-handle-dependencies/</link>
      <pubDate>Mon, 10 Nov 2025 00:00:00 +0000</pubDate>
      
      <guid>https://lukeintheclouds.com/posts/the-import-module-trap-how-powershell-pros-handle-dependencies/</guid>
      <description>
        
          &lt;img src=&#34;https://lukeintheclouds.com/posts/the-import-module-trap-how-powershell-pros-handle-dependencies/powershell_cover.png&#34;/&gt;
          
        
        
        
          &lt;p&gt;Many PowerShell scripts starts the same way - a series of Import-Module statements to load dependencies. This pattern is so common that most developers never question it. But this approach has a problem that shows up when scripts fail halfway through execution in production environments.&lt;/p&gt;
          
        
        </description>
    </item>
    
  </channel>
</rss>