Skip to main content

Save project, run tests and open window to commit macro

I seem to always forgot to save my project when doing a commit to Mercurial so all my commits like like this...

hg commit -Am "Given a user is logged in, when they edit they're profile, then the profile is updated"
hg commit -Am "Project Saved"

I seem to be incapable of remembering to do this (although now I will probably always remember) so I made a little Macro to bring up the commit window instead of my current Visual Studio command. 

It's as simple to make Macros in Visual Studio as it is in any Office program. Just record the Macro (Tools, Macros) and then go in and tweak it if you need it (alt+F11, same as Office).  Mine is the following: 

    Sub SaveAllRunTestsOpenCommandPrompt()

        DTE.ExecuteCommand("File.SaveAll")

        DTE.ExecuteCommand("ReSharper.ReSharper_UnitTest_RunSolution")

        DTE.ExecuteCommand("Tools.ExternalCommand1")

    End Sub

The only non obvious thing here is the final command. This is an external command I set up (Tools, External Commands) opens up a command prompt in the folder containing the project. This means I can then commit the project or do a Wrap Update with OpenWrap. 

I assigned it the keyboard shortcut of ctrl+alt+s so that when I go to save all, it still saves all but it also runs all the tests in the solution, and opens the command window up in the right folder ready to commit. 
Labels:

Comments

Post a Comment

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.
Post a Comment
Read more

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi
Post a Comment
Read more

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second
Post a Comment
Read more