I've been writing scripts since the early days of DOS batch files. Like many of you I simply stick them all in a folder and move on to the next project. Most of my work is just for me or writing projects so this methodology worked just fine for me. But I need to live in your world and in 2016 that means new tools and processes. For many people developing PowerShell tools, modules, and DSC resources this means some sort of versioning system and testing. This is especially true if you are moving into the world of DevOps.<\/p>\n
So I've been learning and using Git and Pester with my new projects. As I find myself revisiting older projects I'm also retrofitting them with a Git repository and a few Pester tests. A major benefit for me is that every time I do this, I learn a bit more about these tools. I've taken some of this knowledge and created a project provisioning script I call New-Project. I know some of you have something similar.<\/p>\n
The script takes a top level folder name, I use a default value of C:\\Scripts, and a project name. Typically this will be the name of a module. The script creates a folder with the project name and then runs through a set of initialization steps:<\/p>\n
So I might use it like this:<\/p>\n
You need to have the Git command line tools installed and the Pester module. I am still debating a few additional features such as integrating the project with my GitHub repositories<\/a> and including a license file. Maybe even an option to generate a module manifest. Perhaps you'll try it out and suggest a few other new features. The file is stored as a Gist on GitHub.<\/p>\n![\"image\"](\"http:\/\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2016\/05\/image.png\" "\\"image\\"")
<\/a><\/p>\n