>>>
>>>My mistake Gregory, I primarily use C# also but occaisonaly VB. I was thinking of static (C#) vs Shared (VB). That was interesting reading however. Thanks
>>>Tim
>>
>>No problem - for classes Shared would apply
>>
>>(I don't know a lot about vb). Read the other day that vb can have 'public' methods, ie methods that do not belong to any class whilst C# cannot
>
>I worked on a project for a few months that was strictly VB. I really prefer C# as it seems like it takes alot less typing but VB has some nice features that would be good in C#. ( NO smack intended for those who use VB)
>
>string MyMethod(int numAllowed, string message)
>
>Seems so much shorter than
>
>Private Function MyMethod(ByVal numAllowed As Integer, byVal message As String) As String
>
>
>anyway, I use both at times, but not real technical on the VB side.
>Regards
>Tim
haha,
A couple of months ago - on a french newsgroup - I posted something similar, just stating that
int i = 1;
was much shorter than
dim i as integer
A reply I got was: since when is shorter better ? The guy had taken it as a personal offence (he had taken the vb road) where I had just pointed out that it was shorter
I know that talking about the vb road is sensitive and sometimes taken as offensive - so I refrain from commenting on that choice
The choice is personal anyway, you take what you are most familiar with
Having programmed in C, it is not a surprise I went for C#
I will not learn vb however - not that I find it bad or so - but I cannot afford the time to do so
There's C#, then there's sql server, reports, etc
Cheers,
Gregory