How the design process works

[Leon Condon]

Hi,
I've moved from the Classic model to the new design model.  I'm understanding it but struggling with some bits.

The main bit for me is the process of creating a class and a DB to support instances of the class.  Simply put this is the process as I see it. 

1. Create the class in the designer with properties and types
2. Do the association mappings to get the relationships between the classes
3. Create mappings between the classes and the DB by creating DB tables and columns and mapping the columns to properties in the class.
4. Build the project and then execute the SQL to get the DB schema.

In the classic version, section 3 didn't exist.  The class was created you designated the properties and whether you wanted them to persist and then they would be created in the DB schema as necessary. 

So as I understand it in the 'new world' I have to create the class and then the DB schema to support it.  Is there a quick way to generate the mappings, like an auto-mapping feature?  The beauty of the classic version is that you can get a working set of classes up and running and then persist them.  Unless I'm missing something, the 'new world' is adding a layer that doesn't need to be there?

Any comments welcome!

[Leon Condon]

Ahhh the map to table option. Right click on a class in the designer. I found it and it maps the fields to the table.

[PetarP]

Hello Leon Condon,

 Yes, this is the option you are looking for. It is also available when you open the mapping editor and check the Use Default Mapping checkbox.

Kind regards,
Petar
the Telerik team