Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would suggest going through the this <a href="http://codeofrob.com/category/10.aspx" rel="nofollow noreferrer">series</a> of post by Rob Ashton specifically </p> <ol> <li><a href="http://codeofrob.com/archive/2009/11/01/dynamically-switching-between-master-pages-in-asp.net-mvc.aspx" rel="nofollow noreferrer">http://codeofrob.com/archive/2009/11/01/dynamically-switching-between-master-pages-in-asp.net-mvc.aspx</a> </li> <li><a href="http://codeofrob.com/archive/2010/02/08/multi-tenancy-in-asp.net-mvc-views.aspx" rel="nofollow noreferrer">http://codeofrob.com/archive/2010/02/08/multi-tenancy-in-asp.net-mvc-views.aspx</a></li> </ol> <p>However, I think though that you may need to do some overriding of how view names are resolved. The key point I think as noted in Rob's post is that views should be resolved and located in reverse order i.e. always look for views defined for your current site and traverse back to the root where a complete set of views are present. </p> <blockquote> <p>set of views per unique domain + one default?</p> </blockquote> <p>Yes - bearing in mind that you may only need specific views for a domain</p> <blockquote> <p>use areas?</p> </blockquote> <p>No - i dont suggest splitting your app up using Areas in this case. I am assuming that you mean an area per domain. You should still split your app into Areas based on functionality and use the same idea resolving the views.</p> <blockquote> <p>any other idea?</p> </blockquote> <p>Using Rob's idea is definitely a good option. I would however take into consideration how many domains(sites) you are expecting to have different view for. I am thinking of the case (not very YAGNI) where every area for each site has different view requirements. So i a well thought plan is needed to stored the views. An example of a possible directory structure. </p> <pre><code>-- Default -- Area1 // Site2's views rendered from here --Views --Shared -- Area2 --Views --Shared ... -- Site 1 // all views from Site 1 are rendered from this folder -- Area1 --Views --Shared -- Area2 --Views --Shared -- Site 2 // only view for Area2 are rendered from here -- Area2 --Views --Shared </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET MVC: customized design per domain
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAhmad
    1. USAhmad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POASP.NET MVC: customized design per domain
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThat's nearly the same what i was thinking about last night. I like this approach. One base set of views(masters, partials + css) and only distinct parts for specific domain. The custom view engine should resolve views from domain name. Thank You.
      singulars
      1. PO
      1. USFeryt
    2. COGlad this idea help. Would you mind updating regarding your progress and any issues you encounter (is this even allowed?)
      singulars
      1. PO
      1. USAhmad
 

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