Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>CodeFileBaseClass</code>, <code>CodeFile</code>, <code>Inherits</code> work together with inheritance, not in place of inheritance.</p> <p>For example, specifying <code>CodeFile="page.aspx.cs"</code> without <code>page.aspx.cs</code> existing will result in: </p> <pre><code>Parser Error Message: The file '/page.aspx.cs' does not exist. </code></pre> <p>Assuming <code>page.aspx.cs</code> exists, specifying <code>CodeFileBaseClass="PageBase.cs"</code> without <code>PageBase.cs</code> existing will result in: </p> <pre><code>Parser Error Message: Could not load type 'PageBase.cs'. </code></pre> <p>On the other hand you may inherit from <code>PageBase</code> <strong>without</strong> specifying the <code>CodeFileBaseClass</code> attribute. This however could result in possible unexpected behaviour when referencing controls on the page from the base class.</p> <p>To quote from <a href="http://msdn.microsoft.com/en-us/library/ydy4x04a.aspx" rel="nofollow">Microsoft's @Page MSDN Documentation</a>: </p> <blockquote> <p><em><strong>CodeFileBaseClass</em></strong><br> <em>Specifies the type name of a base class for a page and its associated code-behind class. This attribute is optional, but when it is used the <strong>CodeFile</strong> attribute must also be present. Use this attribute when you want to implement a shared scenario, where you define common fields (and optionally, associated events) in a base class to reference the controls declared in a Web page. Because of the ASP.NET code generation model, if you defined the fields in a base class without using this attribute, at compile time new member definitions would be generated for the controls declared in the Web page (within a separate partial class stub), and your desired scenario would not work. But if you use the <strong>CodeFileBaseClass</strong> attribute to associate the base class with the page, and you make your partial class (its name is assigned to the <strong>Inherits</strong> attribute and its source file is referenced by the <strong>CodeFile</strong> attribute) inherit from the base class, then the fields in the base class will be able to reference the controls on the page after code generation.</em></p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET CodeFileBaseClass attribute vs. inherit from System.Web.UI.Page
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNope
    1. USNope
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POASP.NET CodeFileBaseClass attribute vs. inherit from System.Web.UI.Page
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. Does this mean that, to be on the safe side, always use the `CodeFileBaseClass` attribute and inherit from the base class?
      singulars
      1. PO
      1. USDaniel T.
    2. COIt seems, that if you intend to share fields in your base class which reference the controls on the page and you do not specify the required page attributes, the integrity of those references is unreliable due to the ASP NET code generation process as described in the quoted text.
      singulars
      1. PO
      1. USNope
    3. COSorry, to answer you question. I would only code what is needed. If I understood the MSDN help correctly, it seems only if you are sharing fields in your base class which are referencing controls on the page should you also specify the required page attributes to prevent undesirable results. If however you only share fields which do **not** reference controls on the page, then their would be no need to assign the page attributes.
      singulars
      1. PO
      1. USNope
 

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