Comments on: Visual Studio/Resharper: Changing the order of arguments

By: DCam

DCam — Fri, 26 Jun 2009 08:53:58 +0000

That last bit from Josh looks a bit HamBreadish?

By: Josh

Josh — Wed, 24 Jun 2009 00:17:57 +0000

What I tend to do these days is use the NUnit.Framework.SyntaxHelpers to make the asserts easier to read and to avoid the issue you refer too.

Assert.AreEqual(theActualValue, “the expectation”);

Becomes:

Assert.That(theActualValue, Is.EqualTo(“the expectation”));

By: Tim Robinson

Tim Robinson — Tue, 23 Jun 2009 22:12:11 +0000

Nice, didn’t know about ‘Ctrl-Alt-Shift-ArrowKey.

How about:
1. Write method TempAssert(actual, expected)
2. Replace all Assert.AreEqual with TempAssert
3. Swap TempAssert’s parameters
4. Replace all TempAssert with Assert.AreEqual (or use my new friend, Inline Method)

By: Andy Palmer

Andy Palmer — Tue, 23 Jun 2009 10:31:52 +0000

Oh, and it would also change this:
DoSomething(param1, param2, “Do something”) to
DoSomething(“Do something”, param1, param2)

Does:
\({:a+}, {:q}
do what you need?

By: Mark Needham

Mark Needham — Tue, 23 Jun 2009 10:31:17 +0000

Yeh good point!

I was only applying it to places which had 2 arguments and in all the cases the second argument was a string so for that case it worked out ok.

I’m sure it could be tightened up to make sure it doesn’t change stuff it’s not meant to – I’m never sure with regular expressions how much time should be spent making it deal with unusual cases as compared to just ensuring you only use it on strings which you know are of a certain format/style.

By: Andy Palmer

Andy Palmer — Tue, 23 Jun 2009 10:24:45 +0000

This will change the order of all parameters where the second one is a quoted string. Be careful when using replace all.

For example, it will also change the order of:
DoSomething(“parameter 1″, “parameter 2″, “parameter 3″);