StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19649989
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-29T04:58:21.277
FavoriteCount
0
LastActivityDate
2013-10-29T04:58:21.277
LastEditDate
LastEditorUserId
0
OwnerUserId
302994
ParentId
19646823
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<p>As Jonathan stated, AutoMapper will help you map your ViewModel entities to your Domain model. Here is an example:</p> <p>In your view you work with the View Model (<strong>CreateGroupVM</strong>):</p> <pre><code>@model X.X.Areas.Group.Models.CreateGroupVM @using (Html.BeginForm(null,null, FormMethod.Post, new { @class="form-horizontal", role="form"})) { @Html.ValidationSummary() @Html.AntiForgeryToken() @Html.LabelFor(model => model.Title, new { @class = "col-lg-4 control-label" }) @Html.TextBoxFor(model => model.Title, new { @class = "form-control" }) @Html.ValidationMessageFor(model => model.Title) @Html.LabelFor(model => model.Description, new { @class = "col-lg-4 control-label" }) @Html.TextBoxFor(model => model.Description, new { @class = "form-control" }) @Html.ValidationMessageFor(model => model.Description) @Html.LabelFor(model => model.CategoryId, new { @class = "col-lg-4 control-label" }) @Html.DropDownListFor(x => x.CategoryId, Model.Categories) @Html.ValidationMessageFor(model => model.CategoryId) <div class="form-group"> <div class="col-lg-offset-4 col-lg-8"> <button type="submit" class="btn-u btn-u-blue">Create</button> </div> </div> } </code></pre> <p>ViewModel (CreateGroupVM.cs): Notice how we pass in a list of Categories - you could not do this had you strictly used your domain model because you cant pass a list of categories in the Group model. This gives us strongly typed helpers in our views, and no ViewBag usage.</p> <pre><code>public class CreateGroupVM { [Required] public string Title { get; set; } public string Description { get; set; } [DisplayName("Category")] public int CategoryId { get; set; } public IEnumerable<SelectListItem> Categories { get; set; } } </code></pre> <p>Domain Model (Group.cs):</p> <pre><code>public class Group { public int Id { get; set; } public string Title { get; set; } public string Description { get; set; } public int CategoryId { get; set; } public int CreatorUserId { get; set; } public bool Deleted { get; set; } } </code></pre> <p>In your HttpPost Create Action - you let AutoMapper do the mapping then save to the DB. Note that by default AutoMapper will map fields that are the same name. You can read <a href="https://github.com/AutoMapper/AutoMapper/wiki/Getting-started" rel="nofollow">https://github.com/AutoMapper/AutoMapper/wiki/Getting-started</a> to get started with AutoMapper.</p> <pre><code>[HttpPost] [ValidateAntiForgeryToken] public ActionResult Create(CreateGroupVM vm) { if (ModelState.IsValid) { var group = new InterestGroup(); Mapper.Map(vm, group); // Let AutoMapper do the work db.Groups.Add(group); db.SaveChanges(); return RedirectToAction("Index"); } return View(vm); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhow do View Models link to the Database?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJack
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POhow do View Models link to the Database?
  singulars
  PostTypePostTypeId
  PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
CommentsPostId
1. COThank you for the detailed description. Cleared up my confusion.
  singulars
  PostPostId
  PO
  UserUserId
  USricky89

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.