We help IT Professionals succeed at work.

Separate Models in ASP.NET MVC

veruthandai
veruthandai asked
on
496 Views
Last Modified: 2013-11-08
I've got a Users table, and a Password table. The password table references the Users table, because each time the user creates/changes their password, the old one is kept in log and encrypted for logging reasons.

I'm a bit new to MVC, so let me show you what the problem is. I'm confused as to how I bind this to my Create View.

Any ideas on how I should approach this with the view page?
LinqSchema01.jpg
UserController.jpg
ViewPage.jpg
Comment
Watch Question

CERTIFIED EXPERT
Most Valuable Expert 2012
Top Expert 2008

Commented:
The Model should have the data, the View should display the model, and the controller should have a reference to the model and the view.
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
@TheLearnedOne

Yes, I understand what you mean, but the problem is that the View references the User Model - and the "Password" model is a different model entirely.

@MogalManic
This isn't a bad approach, but I can't believe this is how people typically handle this in MVC - seeing as it would be an extremely common thing with the way ORM is designed. There is no way to reference a secondary model within a view?
CERTIFIED EXPERT
Most Valuable Expert 2012
Top Expert 2008

Commented:
With MVP/MVC, the model and the view should be separate.  The controller should be the go-between for the model and the view.  I have seen some implementations where the view and controller are combined, but I believe that goes against the MVP/MVC grain.  The model and the view are independent so that you can have multiple views on the same model, or define the same pattern for both a Windows Forms or web site application.

Author

Commented:
Yes, but the Password is part of the Model, but not a static part of it. It is like an array that is attached to the Model. So it is still part of the model. What I need to figure out how to do is to bind one of the text fields so that it will validate with the password object.
CERTIFIED EXPERT
Most Valuable Expert 2012
Top Expert 2008

Commented:
The controller can define an instance of the model, get to the password, and validate it.  The controller should have the business logic, and not the view or the model.

Author

Commented:
Alright, but how does one do that? How do I create an instance of the password to pass to the view when I can only define the View to handle an instance of a User? That's more what I'm getting at. I think we're both trying to say the same thing, except I don't understand where to go from just understanding what has to happen.
CERTIFIED EXPERT
Most Valuable Expert 2012
Top Expert 2008

Commented:
Is the model a single class, or a collection of mutiple classes?

Author

Commented:
The model is a "User", there's a screenshot of the schema in the original post.
User
- Id
- Name
 
Password
- Id
- Hash
- UserId
 
So User.Passwords would be a collection in the Model that is being passed to the View.
For simplicity, I would add a CurrentPassword property which would be something like this:
public string CurrentPassword
{
  get {return this.Passwords[0];}
  set {this.Passwords.Insert(0, value);  //Add new password, pushing old password into Passwords[1]}
}

That way on your View Page you just have to do this:
<% Html.Password(CurrentPassword, "*") %>
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.