Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not sure what your concerns are with adding your own extension methods -- why you'd have to "create your own base view page and completely take over." You can call your custom helpers in any page just as you would the built-in helpers:</p> <pre><code>@Html.TextBoxFor(x =&gt; x.Name) @Html.MyTextBoxFor(x =&gt; x.Name) </code></pre> <p>Furthermore, you can add some sort of flag parameter to your method to control whether it just executes the default functionality or something custom.</p> <p>When you create your own extension methods, you'll have to either change the signature or the name of the method.</p> <p>I used to use unique names, but ultimately found that I really wanted to be able to quickly discern my own implementations from the default, so I sometimes use:</p> <pre><code>@Html.Custom().TextBoxFor(… @Html.Custom().TextAreaFor(… </code></pre> <p>Basically, you create one new extension method that takes an <code>HtmlHelper&lt;T&gt;</code> and returns a <code>CustomHelpers&lt;T&gt;</code>.</p> <pre><code> public static CustomHelpers&lt;TModel&gt; Custom&lt;TModel&gt;(this HtmlHelper&lt;TModel&gt; html) { return new CustomHelpers&lt;TModel&gt;(html); } </code></pre> <p>The <code>CustomHelpers&lt;T&gt;</code> class defines all of your own implementations:</p> <pre><code> public class CustomHelpers&lt;TModel&gt; { private readonly HtmlHelper&lt;TModel&gt; _html; public CustomHelpers(HtmlHelper&lt;TModel&gt; html) { _html = html; } public MvcHtmlString TextBoxFor&lt;TProperty&gt;(Expression&lt;Func&lt;TModel, TProperty&gt;&gt; expression) { // because you have a reference to the "native" HtmlHelper&lt;TModel&gt;, you // can use it here and extend or modify the result, almost like a decorator; // you can get the "native" result by calling _html.TextBoxFor(expression) } </code></pre> <p>So, your "override" of <code>TextBoxFor</code> can receive a flag from your partial view to determine whether it returns the native result or something specific to the context.</p> <p>Again, the <code>CustomHelpers&lt;T&gt;</code> class is entirely optional. You'll be adding a flag parameter or something similar to the signature of your custom helpers, so you won't collide with existing helpers.</p> <p>The benefit it confers is to potentially namespace your helpers. You could have:</p> <pre><code>@Html.TextBoxFor(… @Html.JQuery().TextBoxFor(… @Html.Mobile().TextBoxFor(… </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POIs there a way to dynamically wrap/intercept HtmlHelper extension methods. Think decorator pattern
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJay
    1. USJay
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COIt also helps to declare your custom helpers in namespace `System.Web.Mvc.Html`
      singulars
      1. PO
      1. USJay
    2. COJay i really liked the way you implement helper methods.
      singulars
      1. PO
      1. USMuhammad Adeel Zahid
    3. COThe key is to re-use the existing views, without having to go thru and change them to custom. Currently, seems only possible thru hacks, see my comment to @marcind. Btw if you go custom, without inheriting from HtmlHelper, then everything needs to be re-implemented. Your technique works for other scenarios, but probably still better to inherit from HtmlHelper or HtmlHelper<T> IMHO.
      singulars
      1. PO
      1. USDax70
 

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