>>Camel case has a lower case first letter: But do you really think sendemailmessagetoviv is more readable than SendMailMessageToViv? (one of my pet peeves with VFP was it's insistence on translating method names to lower case for no reason)
>>It's also common to see camel case used for private variables - in fact backing fields often have the same name (differing only by case) as their public counterpart. E.g:
>>public string SomeProperty
>>{
>> //////
>>}
>>private string someProperty;
>>
>>Personally I like this construct - it's easy to identify the link between the two names elsewhere in code.
>>
>>Regardless of whether you think it is stupid probably 95% of NET code follows the general convention - can you point me to a single example on the web that doesn't? AFAICS the MS guidelines (http://msdn.microsoft.com/en-us/library/xzf533w0(VS.71).aspx) are pretty generally followed - not because MS say so but because they make sense. I seriously doubt you would get a job in a .NET shop without complying.
>>
>>Regards,
>>Viv
>
>CamelCase, as defined in a Wikipedia entry, is not with a leading lower case letter. But, there are probably differing understandings of what that means, so let's not split hairs. The point is that I know what you're referring to. It has been fairly popular in C dialects, I believe (lowercase first letter).
>
>As for "probably 95% of NET code follows the general convention" I would doubt that seriously. There is tons and tons of .NET code out there and I'd be surprised if it was anywhere near the figure you quote. You made the statement, so don't ask me to disprove it. You prove it and show me some evidence instead of pulling it out of thin air.

How do you propose I should prove that? But, on your behalf, I trawled the web looking for examples of C# code that *didn't* follow the convention and failed to find any. And I haven't got a C# book that doesn't follow it either.
>
>As for getting a job in a .NET shop . . . oh, God, I hope I never have to do that.

Me too :-}