The master, for many companies I support, is my c:\scripts\companyname folder. Then I have another script that leverages robocopy to move updated and new scripts to the companyname servers.
I think that git is probably better suited to scripts than TFS. But that is not my own opinion, just what I've seen some PowerShell MVPs say. For me and my clients, robocopy and a centralized repository works just fine. If my clients were ALSO editing the scripts that I write, then we would need some type of a source code control system. But that has not yet occurred. From: [email protected] [mailto:[email protected]] On Behalf Of Alice Goodman Sent: Monday, May 11, 2015 8:35 PM To: [email protected] Subject: [Exchange] Store Power Shell Scripts in TFS? Where do you store Power Shell scripts for team reference? Currently, I keep all Exchange scripts on the Exchange Servers in the C:\scripts directories. I keep them synched, manually, meaning if I add a new one to MBX01, I copy it around to the others. I also keep a copy on my own C:\scripts drive. Someone here wants to talk with the team about creating a repository in TFS to store these types of tools and make them available to the broader team. Just wondering.. Alice
