<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>PowerShell Inside</title>
  <link>https://www.powershellinside.com/</link>
  <description>Deep dives into PowerShell, automation, and Windows sysadmin craft.</description>
  <language>en</language>
  <lastBuildDate>Mon, 26 Oct 2026 20:06:53 GMT</lastBuildDate>
  <atom:link href="https://www.powershellinside.com/feed.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Your Script Worked Fine on Windows. Then It Met Linux.</title>
    <link>https://www.powershellinside.com/cross-platform-powershell-what-breaks-on-linux/</link>
    <guid isPermaLink="true">https://www.powershellinside.com/cross-platform-powershell-what-breaks-on-linux/</guid>
    <description>PowerShell 7 promises one language across Windows, Linux, and macOS — but the fine print bites. Here&#039;s a field report on exactly what breaks when Windows-honed scripts head to a hybrid environment, and how to future-proof your code before the migration.</description>
    <author>PowerShell Inside</author>
    <category>Cross-Platform Automation</category>
    <pubDate>Mon, 26 Oct 2026 20:06:53 GMT</pubDate>
  </item>
</channel>
</rss>