I have been working on a LOT of automation scripting, and for whatever reason whenever I did this int he past I always used batch files – I guess I was just used to it? Whatever…
I got smart (finally) and started using Powershell and I have been able to do some pretty cool automation (post with scripts incoming). Powershell has a quirky syntax, and I have been doing lots of googling. I just ran across the Powershell Cookbook. Pretty good stuff…
We have some core libraries that a lot of other libraries depend on. While these change very infrequently, they were written a while ago and some refactoring is in order. The problem is I don’t want to have to doa lot of manual updating. I thought I’d look into automating Nuget packages.
The article has sample scripts which I’ll be able to adapt and setup to generate Nuget packages on build. I can then copy the packages to a local Nuget server ad then I’ll be able to set up the other libraries to use Nuget so they can easily get any future updates!
So the whole reason I started this stupid blog was so I’d have a place to fall back on with all the interesting crap I found on the interwebz. Yeah, that worked out well…
So why the hell am I not just adding every cool thing I find?!? Because it is way easier to bookmark it. Hell, I use this pre-alpha version of Oxite and I gotta type in my HTML markup by hand. How archaic is that! [Edit: not any more!]
Well, here is a great link to TortoiseSVN automation. I have been working towards completely automating our release procedure, and we always had the Tortoise dialog that we had to click “OK” for every time. We all know how completely annoying that can be, right? Well, no more!
What good is this post without some sort of example, right? Well here you go.
We used to do something like so:
"C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe" /command:update /path:%FOLDER%
That has the annoying dialog. So now we just do the following:
"C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe" /command:update /closeonend:2 /path:%FOLDER%
That handy little /closeonend saves my click-finger! Voila! The post goes into detail on the parameter, so have a look.