<feed xmlns="http://www.w3.org/2005/Atom"><title>ps1</title><id>https://evotec.xyz/fr/tags/ps1/index.atom.xml</id><updated>2018-11-16T00:05:31.0000000Z</updated><subtitle>Evotec Main Website</subtitle><link href="https://evotec.xyz/fr/tags/ps1" /><link href="https://evotec.xyz/fr/tags/ps1/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>PowerShell – Single PSM1 file versus multi-file modules</title><id>https://evotec.xyz/fr/blog/powershell-single-psm1-file-versus-multi-file-modules</id><link href="https://evotec.xyz/fr/blog/powershell-single-psm1-file-versus-multi-file-modules" /><updated>2018-11-16T00:05:31.0000000Z</updated><summary>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.</summary><category term="powershell" /><category term="ps1" /><category term="psm1" /></entry></feed>