Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm having a little trouble picturing your setup. My guess is you have the current setup:</p> <p><strong>Controllers</strong><br /> &nbsp;&nbsp;&nbsp;&nbsp;- HomeController.cs <br /> &nbsp;&nbsp;&nbsp;&nbsp;- MobileController.cs<br /> <strong>Views</strong><br /> &nbsp;&nbsp;&nbsp;&nbsp;- Home<br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --Index.aspx<br /> &nbsp;&nbsp;&nbsp;&nbsp;- Mobile<br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --Index.aspx<br /></p> <p>But you want: <br /> <strong>Controllers</strong><br /> &nbsp;&nbsp;&nbsp;&nbsp; - HomeController.cs<br /> <strong>Views</strong><br /> &nbsp;&nbsp;&nbsp;&nbsp;- Home<br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --Index.aspx<br /> &nbsp;&nbsp;&nbsp;&nbsp;- Mobile<br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --Index.aspx<br /></p> <p>Is that correct?</p> <h2>Update:</h2> <p>Aas people mentioned below it's one of those 'that's just how MVC works' sort of deal. 'Home' is a location you can go to, but 'Mobile' is a specific type of page. If you add another area called "About" as new Views subfolder, where would you put your mobile folder? What is mobile now supposed to handle? If mobile is not supposed to replicate the regular site, then it should have its own controller, even if it replicates some code (don't forget you can create classes outside the controllers that can do the brunt of the work that any controller can call). <br /><br /> On the other hand if you want a mobile version of each of your pages you should be adding them under the views folder for each route. For example:</p> <p><strong>Controllers</strong><br /> &nbsp;&nbsp;&nbsp;&nbsp; - HomeController.cs<br /> <strong>Views</strong><br /> &nbsp;&nbsp;&nbsp;&nbsp;- Home<br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Mobile<br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Index.aspx<br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --Index.aspx<br /></p> <p>I'm not exactly sure where you are doing the logic to figure out if they are on a mobile platform, but assuming for now it's in the controller somewhere in your HomeController.cs you then have:</p> <pre><code>public ActionResult Index() { if([check for mobile]) { return View("Mobile/Index"); } else { return View("Index"); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POChange view in MVC
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USboolean
    1. USboolean
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POChange view in MVC
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COyou got it right for my current setup, it is exactly like that. for the new setup i can have it exactly as you suggested or have the Mobile folder under Home folder. I guess it does not make any difference as long as i have separate views for Home and Mobile but use only HomeController.cs. I do the browser detect in Home>>Index ActionResult
      singulars
      1. PO
      1. USJohn Hey
    2. COpublic class HomeController : Controller { public ActionResult Index() { if (MobileHelper.IsMobileDevice(Request.UserAgent)) { return RedirectToAction("Index", "Mobile"); } return View(); } public ActionResult About() { return View(); } } above is my current code to redirect to Mobile controller. Now I want to redirect to Home controller but use Mobile view.
      singulars
      1. PO
      1. USJohn Hey
    3. COThis breaks regular MVC structure. Most view engines will now think Mobile is the name of a controller. This is also a comment rather than an answer.
      singulars
      1. PO
      1. USYuriy Faktorovich
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload