+1 for source control. Our project scenario scripts usually end in one of:
- $ / project / Trunk / Addition
- $ / project / Trunk / Tests / Bin
- $ / project / Trunk / Tools / Bin
For personal scenarios, I am currently using two approaches. First I create ~ \ Bin, put this in the path and set my personal PowerShell scripts. The second approach is that I use Live Mesh to synchronize the PowerShell folder between all my machines. It has scripts, presentations, etc. I should probably create a subdirection of Bin in the mesh folder and put this bin directory in its path.
V2 introduces module support, so any modules I create will be under ~ \ Documents \ WindowsPowerShell \ Modules.
Regarding the question of using scripts from others and versions, read the modules and Modular manifests in V2. I think this new feature will help.
Keith hill
source share