Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Thank you, good answer - would I need a books controller at all? Commented Apr 29, 2013 at 21:48
  • Well... I'd forget all about MVC first, and think about your basic entity relationships (Libraries>BooksInLibaries>Books... etc.. etc..) This will probably dictate if you want multiple controllers and everything will become clearer. What the actual book methods above return is based on your need, but could just be references (ie, an ID) which you could then use in a link to the actual book. That link would then resolve to a book controller and a GetBook method where you display the complete book info (which is then your singular unique record). Commented Apr 29, 2013 at 23:58