If you will be using EF, then learn what it expects by default before creating your table and use CodeFirst as the designer is going away.


>Hi
>About to start a new app.
>Plan to use Entity Framework, and will be using Winforms initially and some Web Forms (Or MVC ) down the line
>Will be using MS Sql Server for the Database
>
>Wondering whats best approach with Naming Conventions
>
>e,g,
>For DataBase (Use MyGreatDataabse MYDATABASE My_Databas etc
>for Table Names (Use CustTable Customers, Customer , Customer_Table CUSTTAB etc
>for Field Names (Use Ad1 or CustAd1 or CustomerDeliveryAddress1 or CUST_ADDRESS1 etc)
>If using for instance Address1, there will probaly be 5 different tables with an Address1
>
>Any particular casing recommended
>
>Tia
>Gerard