Hi Guys,

I'm a colleague of Omar. And this is my first post ever!!

Simple question for you people...

When I generate code from LLBL Pro, the property names generated are in Pascal Casing although the field names in my database are in Camel Casing. For example, one of my field names is GL.strEmployeeName but the property name generated for this field is GL.StrEmployeeName.

This is disturbing to say the least. I was wondering... is there a way to stop this from happening.

Please bear in mind that the check box for "Correct Name Casing" is NOT checked.

Thank you, Bashar Lulu

Bashar wrote:

Simple question for you people...

When I generate code from LLBL Pro, the property names generated are in Pascal Casing although the field names in my database are in Camel Casing. For example, one of my field names is GL.strEmployeeName but the property name generated for this field is GL.StrEmployeeName.

This is disturbing to say the least. I was wondering... is there a way to stop this from happening.

Field names in an entity and the properties representing them are pascal cased, because of the design guidelines released by Microsoft, which are also build into rules in FxCop. To make the code as much compliant with FxCop and the guidelines for library code, I kept the properties/fields Pascal cased.

At the moment there are no options to set to avoid this, such a setting is planned for the next upgrade of the designer. Still I'd like to suggest to you to keep the pascal cased properties as that's the prescribed coding style for .NET code.

Looks like MS only wants us to use camel case in a couple of instances.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/cpconcapitalizationstyles.asp