asp.net MVC combines EDMX data Model validation __.net

This is one of the issues that I have recently solved, the ado.net entity Validation model added in MVC3. Of course this is a customer request, do not like this thing, each mapping database will generate a lot of code. However, the function is still relatively powerful, do not write data access code themselves. is a quick development to select a framework. Ok. Get to the point.

asp.net MVC combines EDMX data Model validation in two different ways:

First type:

is to modify the database's table structure to a null type ...   Then add an attribute above the attribute ... Direct validation can be ...

The exception is thrown when debugging, but it does not affect the project when it is published or running normally.

Had

Disadvantages:

1. Inability to perform very complex validation

2. To modify the structure type of the database

3. It's not easy to throw an exception when you debug.

Advantages:

1. More convenient, do not need to add redundant validation entity classes

The second type:

is to add a validation entity class at the time of validation. The rest is configured according to the characteristics of MVC, and then add mappings in class to map the types of your entity classes

I now test is these two methods, another ordinary model or directly add features are good. Do you have any questions you can communicate with ~~~~~~~~~~~~