<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ps1</title><link>https://evotec.xyz/de/tags/ps1</link><description>Evotec Main Website</description><atom:link href="https://evotec.xyz/de/tags/ps1/index.xml" rel="self" type="application/rss+xml" /><item><title>PowerShell – Single PSM1 file versus multi-file modules</title><link>https://evotec.xyz/de/blog/powershell-single-psm1-file-versus-multi-file-modules</link><description>I’ve been working with PowerShell Modules for a while now, and most of my knowledge about them came from Warren F (psCookieMonster) blog about Building a PowerShell Module. It is a handy piece of information and recommended read for anyone starting up writing PowerShell Modules. He introduces an idea where a module is stored in multiple folders Private, Public, Bin, Lib and so on and having YourModule.psm1 as a wrapper for functions, binaries in those folders, where each function is stored in its file. It’s an excellent concept, and I use it every day. It allows me to jump into a file quickly I want to find and fundamentally easier for development, especially in teams.</description><pubDate>Fri, 16 Nov 2018 00:05:31 GMT</pubDate><guid>https://evotec.xyz/de/blog/powershell-single-psm1-file-versus-multi-file-modules</guid><category>powershell</category><category>ps1</category><category>psm1</category></item></channel></rss>