StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16328671
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-02T00:44:23.163
FavoriteCount
0
LastActivityDate
2013-05-02T01:38:31.827
LastEditDate
2013-05-02T01:38:31.827
LastEditorUserId
1773119
OwnerUserId
1773119
ParentId
8316236
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I have been spending quite a bit of time thinking about this exact same issue. I am using ninject to inject my repository into my web UI layer so that my web UI only accesses the database through an interface. I am wanting to be able to validate things that access the database such as checking for duplicate names and hence my validation needs to access the injected repository. I think that the best way to do this is to just setup Fluent Validation via the manual method rather than the MVC integrated way. For Example: Create your validation Class (can pass in repository Interface): <pre><code>public class CategoryDataBaseValidation : AbstractValidator<CategoryViewModel> { private IRepository repository; public CategoryDataBaseValidation (IRepository repoParam) { repository = repoParam; RuleFor(Category => Category.Name).Must(NotHaveDuplicateName).WithMessage("Name already exists"); } private bool NotHaveDuplicateName(string name) { List<Category> c = repository.Categories.ToList(); //Just showing that you can access DB here and do what you like. return false; } } </code></pre> } Then in your controller you can just create an instance of above class and pass in the repository (that ninject would have injected in the controller constructor) <pre><code> [HttpPost] public ActionResult Create(CategoryViewModel _CategoryViewModel ) { CategoryDataBaseValidation validator = new CategoryDataBaseValidation (repository); ValidationResult results = validator.Validate(_CategoryViewModel ); if (results.IsValid == false) { foreach (var failure in results.Errors) { //output error } } return View(category); } </code></pre> Both the above files can live in the Web UI project and you can then also just use the standard MVC DataAnnotations for client side validation. Just thought that I would put this up for comment / help someone.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFluent Validation in ASP.net MVC - Database Validations
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UScraigvl
UserOwnerUserId
1. UScraigvl
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.