Databases
StackOverflow2013
Postsdbo
POASP.NET MVC Custom Validation in View Model Best Practice
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POASP.NET MVC Custom Validation in View Model Best Practice
    primarykey
    data
    text
    <p>I am trying to use a combination of Domain Driven Design with Test Driven Development for this application I am building in ASP.NET MVC 3. My archictecture is set up with Repositories, Domain Models, View Models, Controllers and Views. All validation will be handled in the view model. I set up my view model to inherit from "IValidatableObject" so that my validation attributes and my custom validation that i set up in the "Validate" method are both executed when my controller method calls "ModelState.IsValid". The problem I am running into is accessing my repository in the Validate method of my view model. I need to access the repository to check for duplicate records in the database. It seems like the best idea would be to create a property of IRepository type and set that property by passing injecting my repository into the constructor of the view model. For example:</p> <pre><code>public class UserViewModel : IValidatableObject { public UserViewModel(User user, IUserRepository userRepository) { FirstName = user.FirstName; LastName = user.LastName; UserRepository = userRepository; UserName = user.UserName; } public string UserName { get; set; } public string FirstName { get; set; } public string LastName { get; set; } public IUserRepository UserRepository { get; set; } public IEnumerable&lt;ValidationResult&gt; Validate() { UserCriteria criteria = new UserCriteria { UserName = this.UserName }; IList&lt;User&gt; users = UserRepository.SearchUsers(criteria); if (users != null &amp;&amp; users.count() &gt; 0) { yield return new ValidationResult("User with username " + this.UserName + " already exists." } } } </code></pre> <p>Do you guys think this is a good idea?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USErik Funkenbusch
    1. USRiceRiceBaby
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POASP.NET MVC Custom Validation in View Model Best Practice
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POASP.NET MVC Custom Validation in View Model Best Practice
      1. USTFD
      1. VTFavorite
    3. VO
      singulars
      1. POASP.NET MVC Custom Validation in View Model Best Practice
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPersonally I would avoid having a property that performs a database lookup.
      singulars
      1. POASP.NET MVC Custom Validation in View Model Best Practice
      1. USJustin Helgerson
    2. COI see what you're saying, but how else would I validate against duplicate records. I was thinking about creating a custom validation method that the controller method would call and pass in the modelstate. The method would then perform my custom validations and add the model errors to the modelstate (side effect- c# object = pass by reference), but it seems like what i posted would be alot cleaner and code would be simpler.
      singulars
      1. POASP.NET MVC Custom Validation in View Model Best Practice
      1. USRiceRiceBaby
    3. COThe Domain Validation **must be encapsulated in the domain**. Validation is a concept that must be applied at several places in the application. Typically when you validate a View-Model, you are validating to check that the data provided by the user is safe, (apply sanitizer) and _apparently correct_. Then you usually would call your aggregate root to perform some actions. There you should validate the domain invariants (domain rules). In a CQRS architecture, I have found it's a good practice to validate inside the CommandHandler
      singulars
      1. POASP.NET MVC Custom Validation in View Model Best Practice
      1. USJupaol
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload