Using Right Function in vb.net

How will it affect performance?!

Anyhoo, you just need to fully qualify the Right() function so it doesn't clash with the Right() property of the Form (which tells its location):
http://msdn.microsoft.com/en-us/library/microsoft.visualbasic.strings.right(VS.85).aspx

    Label1.Text = Microsoft.VisualBasic.Right(someString, 2)

Idle_Mind/Mike

>>
How will it affect performance?!
<<

I haven't tested on this one but I was surprised to find that at least some of the "old" VisualBasic stuff that is just included for backward compatibility is actually faster than its VB.NET replacements.  See the last couple of lines in this thread

http://www.experts-exchange.com/Programming/Languages/.NET/Visual_Basic.NET/Q_21489283.html

The discovery was quite by chance.  I did, at the time dig a bit further into it, and found it was because TrimStart and TrimEnd do more work "behind the scenes" than LTrim and RTrim do.  It's nearly three years ago now, and I can't remember all the details, but I think they catch more potential "white space" characters.

But it has made me a bit wary of assuming that VB.NET functions will perform "better" (or even at least as well as) their VisualBasic predecessors.

Roger

Roger that...I'll have to test some of them out.  =)

I do have to admit that Right() is a heck of alot more readable than SubString() when you just want the last XXX characters.

I've now had a chance to test.  Not, I stress, at laboratory levels.  So you can check if I was comparing like with like, the test frameworks for the two methods were the same but the operative lines were

            result1 = Microsoft.VisualBasic.Right(teststring, extent)

and

            result2 = teststring.Substring(teststring.Length - extent)

I don't think there's really anything in it either way.  If there is, it looks to be in favour of Right, but it is so small as to be meaningless: I had to do 10000000 (Ten million) iterations before anything was discernable at all.  And then the results, discarding the first, were

Using Right - 1672 milliseconds
Using Substring - 1719 milliseconds
Using Right - 1609 milliseconds
Using Substring - 1656 milliseconds
Using Right - 1656 milliseconds
Using Substring - 1625 milliseconds
Using Right - 1609 milliseconds
Using Substring - 1656 milliseconds
Using Right - 1594 milliseconds
Using Substring - 1641 milliseconds

But, for my money, Right would win out on two scores.  First, it is (even with including the namespace) easier to code and read.  Secondly, it won't error (whereas Substring will) if it is asked for a greater number of rightmost characters than are in the total string.  That problem can be overcome in code with SubString but (a) it makes for more code and (b), although I didn't test the point, would I think slow it down a bit.

Not really quite on topic.  But I thought it worth sharing ;-)

Roger

I think it's worth sharing too Roger.  Thanx for posting.  =)