Ah, naming conventions... while I personally do not like underscores in any name - whether it be a class or database table name or column name, and the like... Still, it seems that it would make more sense to have a "smart default" rather than be "enforced" since naming conventions are really such a subjective thing. Also, the in the real world there is a lot of naming ugliness out there that we OCD-types have to contend with. :)

I'm not suggesting that time be spent on changing this. But I do think going forward it's good to think more in line with "smart defaults" and convention (hmmm... sounds like I'm buying into some of the RoR hype :) but I do think they have something there).

OK... tuning out... back to our regularly scheduled MM.NET programming...

>
>>When I generate business objects after installing 2.3, underscores are removed from the object names (i.e. Invoice_Items = InvoiceItems).
>>
>>Is there a way to turn off this feature? (I like all the other changes I've seen so far)
>
>Actually, this was intentional (and requested) because the use of underscores in the names of public classes or class members breaks Microsoft naming conventions. Can I talk you out of wanting underscores <s>?
>
>Best Regards,