���I don't know who "he" is, but he's pretty much correct.� However, I'm not
sure that concatenation has ever been done the way you describe it for VB6 (I
thought it was always a big perf hit).
���If you're going to be doing a *lot* of string building, then yes, you should
definitely use StringBuilder.� If you just put a first and last name together
to greet a user on each page, then it's probably not worth your trouble.
���Of course you can always test this stuff yourself; just set Trace=True on
your page and do a Trace.Write before and after you perform these operations.�
I don't know if you can directly assess available memory, but you can certainly
see how much time each process takes.
Cheers,
Peter
From: DJ Sampson [EMAIL PROTECTED]
I have heard that the Stringbuilder class, now, is preferred - instead of
concatenation.
He told us that, (in DotNet) with concatenation (using +=), that the memory
space, with each addition/concatenation, was totally reallocated, instead of
being extended, like in VB6.
How much of this is correct and how much can concatenation negatively affect an
application?
(Does it really matter that much?)
[Non-text portions of this message have been removed]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
