When I first started dipping my fingers into the GitHub pool, it was because I really felt there was a need. Version control was becoming an issue and having to re-write code I’d already perfected because of a glitch somewhere on the way–translation: accidentally deleting the wrong file–was something that just had to be addressed. And, I think like a lot of PowerShell scripters, I soon started asking questions like: WTF is this? What is going on? Who came up with this crap? I’m no expert, but read on if you’re interested in learning how to use PowerShell and GitHub together.
This has come up at Spiceworks a couple of times, the which should I learn discussion. vbScript or Powershell? Considering the theme of this blog I don’t think you need to ask which camp I stand in. But what about this steep learning curve? Here are my thoughts.
I wrote about multithreading using Runspace here, but I also wanted to talk about running them the Powershell way using jobs. I want to make sure I give credit where it’s due, because most of my work in Jobs is based on Ryan Witschger‘s work. He writes a great Powershell blog called Get-Blog.com (great site name, too). Anyway, read on for my riff on Powershell jobs and the 3 step process you need to use them.
I think I’ve mentioned this before, but at work we are divesting one of our business units which is requiring us to split up a lot of data. One of the bigger challenges has been what to do with our Sharepoint site. At SeraCare we make very extensive use of our Sharepoint server and have a nearly 80gb database! This made the upgrade from Sharepoint 2003 (not WSS 3.0) to Sharepoint 2010 pretty challenging, let me tell you! Now I have to pick up over 800 sites from our Intranet and send it over to the IT department of this divested business unit. Here’s how I plan to do it.