Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I generally advise creating a BasePage class of some sort that encapsulates the behavior you want through all of your pages, these objects are assumed to always have the same master page, if you need other setups then you can create other objects as necessary.</p> <p>From there you can create some properties or methods to allow the BasePage objects to access the master page or its associated properties in a very easy to code way such as this.Title = "MyTitle"</p> <p>You can get fancier and create some virtual methods on your BasePage class that you can then override on the physical pages as necessary, to set titles, etc, as needed, without ever grabbing the Master page object directly (which yes, is annoying and ugly). This might look something like this.Title = GetTitle(); (GetTitle is a virtual method on the BasePage that is overridden in the child pages as needed for those pages you want to set a title for).</p> <p>This makes strong use of inheritance and lets you add functionality to all of your pages very easily, it may be overkill for what your doing but I've never found a situation that was too simplistic for this architecture, it just works really well. I personally find this design far better than constantly using FindControl(), which tends to be error-prone when control ID's change, etc.</p> <ol> <li><p>FindControl() is bad because if the control ID's change, then you might forget to update them in the FindControl reference, and now it'll break the next time its executed, I stay well away from static stuff like this if at all possible for this very reason, it's a cheap, quick but error-prone solution.</p></li> <li><p>Accessing the Master page directly isn't inherently bad, I just can't stand stuff like:</p> <p>myMasterPage myMaster = (myMasterPage)this.Master</p></li> </ol> <p>Gets old, is uglier than it needs to be, wrap it in an accessor property at the very least ;)</p> <p>I like the following better:</p> <pre><code>Title = "My Title"; // Property </code></pre> <p>or</p> <pre><code>Title = GetTitle(); // Virtual method </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POBest way to set master page properties in content page in asp.net?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCapital G
    1. USCapital G
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBest way to set master page properties in content page in asp.net?
      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
    1. COHi Capital G, Thanks For ur Reply, so u mean to say that I should create a base page with properties and set the properties in the appropriate pages and then My MasterPage will access the properties of the basepage and set the value for the appropriate controls in the master page. Will this not create any problem when muliple instances of the same page will exists pls clariy me with it.
      singulars
      1. PO
      1. USIsh Tech
    2. COSorry in getting to you so late, I was on vacation. I'm not sure what you mean by multiple instances of the same page. If you mean many pages will have the same master page, no, it's not a problem as long as all your pages inherit from the BasePage, because then they are all talking to the same Master page. If you need multiple master pages then you can simply make multiple versions of your BasePage like 'SiteBasePage' or 'AdminBasePage' or whatever you need. Also none of this is automatic, you will have to hook up the architecture between base page and master page, but after that its easy.
      singulars
      1. PO
      1. USCapital G
 

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