Some time ago I discovered a neat language feature of VB.NET where you can name parameters for method calls. This is actually something which has been around a long time even before .NET (was there anything before .NET? :) ).
Named parameters is a feature you can use if you want to be really explicit in your method calls it does actually improve readability somewhat.
As an example I had to code a components which would do transactions on people's credit card for Bolia.com because they have way too many transactions each week for them to handle it all manually.
The interface I was programming against looking something like:
Function Capture(ByVal sAmount As String, _
ByVal sTransact As String, _
ByVal sOrderid As String, _
ByVal bForce As Boolean, _
Optional ByVal sAccount As String = "") As Long
You can use named parameters if you want to be really explicit in your method calls it does actually improve readability somewhat. In the case I mentioned I wanted to make it really clear which values were used for what in the method call like this:
Dim amount As String = "11111", transactionId As String = "11111"
Dim orderId As String = "11111", forceCapture As Boolean = True, accountNumber = "1111"
Capture(sAmount:=amount, sTransact:=transactionId, sOrderid:=orderId, bForce:=forceCapture, sAccount:=accountNumber)
Unfortunately C# does not support this but I guess that it goes against the whole philosophy of C# anyway :)
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.