1

I am building an applicaiton using asp.net mvc3. I added two layers to this project, repository and service layer. some of my code, I am not sure which layer I should put them in.

on my register page, to create an account, I only ask user to enter their email and password, its using UserRegisterViewModel. before I add it to the database, my user table need more info.

I need to create an User entity from the UserRegisterViewModel:

user.ip= "1.1.1.1";
user.createddate="11/11/1911";
....

so above code, where should I put them? webui, repoistory or service layer.

qinking126
  • 11,385
  • 25
  • 74
  • 124

2 Answers2

2

You can only get the IP address from the request so you have 'get' it there in the Action

Something like this

[HttpPost]
public ActionResult Login(UserRegisterViewModel model) {
    if(ModelState.IsValid) {
        SaveLogonToAudit(model.Username);
    }
    return View(model);
}

private void SaveLogonToAudit(string username) {
    var user = new UserAccount(username, Request.Browser.Browser, Request.Browser.Type, Request.UserHostAddress);
    user.Save();
}

The User entity could live in another layer, your UserRegisterViewModel will live in the MVC UI layer. It's perfectly normal to have a ViewModel that represents the data in your view and a completely separate class in another layer that represents your User entity. That's good design. Your User entity can be in the ServiceLayer and have business rules associated to it. That class will then call into your repository layer to save its data.

I agree with Leon Cullens, the CreateDate should live in the User entity, that's why you don't see me setting it. The User entity should handle it's own CRUD actions that call into your RepositoryLayer. Set the CreateDate in the ctor or better yet, have a base class that has CreateDate, CreatedBy, LastUpdateDate, LastUpdatedBy that the User will use internally.

CD Smith
  • 6,597
  • 7
  • 40
  • 66
2

I would add the 'CreatedDate' in the constructor of your 'User' entity, and add the IP address in the controller that receives the ViewModel object.

I case you didn't know: you can map ViewModels to Entities using AutoMapper.

Leon Cullens
  • 12,276
  • 10
  • 51
  • 85
  • thank you, i will try automapper, but when I am mapping between User and UserRegisterViewModel, where should I do it ? web ui layer, domain layer or service layer? – qinking126 May 17 '12 at 16:02
  • In your Controller, so that's probably the web UI layer :) Keep in mind that you should initialize AutoMapper mappings only one time, so bootstrap them in your application start. Then you only need to do this in your controller: Mapper.Map(userobject); You can also map to an existing entity by passing that as the second parameter to the Map() function. – Leon Cullens May 17 '12 at 16:03