Welcome! and rules
Joel on Software
I found this article interesting, http://www.fawcette.com/vsm/2002_11/magazine/features/eaton/default.asp , mostly because it describes what i'm currently doing in VB6.
I've not done benchmarks, but I, too, have done nearly the same reporting stuff in VB6, using design similar to that described in this article.
If my understanding of the .net licencing agreement is correct, you are explicitly forbidden to publish the results of ANY sort of performance comparisons you make. This would include comparisons of .net languages with earlier versions of Microsofts own languages.
oh geez, i had forgotten about that. hmmm... are you saying i can't even use this information to try to sell my bosses? ugh.
vb.net and c# will have the same performance results because it ends up being the same IL code anyway.
Actually, people have documented IL differences between the VB.NET and C# compilers -- though they both compile to MSIL, they take different approaches to optimizing things. The few investigations I've seen of this suggest that the C# compiler is less likely to push unnecessary variables around.
I wish Option Strict On disallowed the FunctionName = ReturnValue convention; I don't think I've ever used it in VB.NET. But that's probably the biggest source of 'unnecessary' temporary variables in VB.NET IL.
"I wish Option Strict On disallowed " [whatever]
Fog Creek Home