Databases
StackOverflow2013
Postsdbo
POThe type arguments cannot be inferred from the usage. Try specifying the type arguments explicitly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POThe type arguments cannot be inferred from the usage. Try specifying the type arguments explicitly
    primarykey
    data
    text
    <p>Could someone please clarify something for me. In my ASP.NET MVC 2 app, I've got a <code>BaseViewModel</code> class which includes the following method: </p> <pre><code>public virtual IDictionary&lt;string, object&gt; GetHtmlAttributes&lt;TModel, TProperty&gt; (Expression&lt;Func&lt;TModel, TProperty&gt;&gt; propertyExpression) { return new Dictionary&lt;string, object&gt;(); } </code></pre> <p>The idea being that each child viewmodel can override this method and provide a suitable set of html attributes, based on some logic, to be rendered in the view:</p> <pre><code>&lt;%: Html.TextBoxFor(model =&gt; model.MyProperty, Model.GetHtmlAttributes (model =&gt; model.MyProperty)) %&gt; </code></pre> <p>However when used as in the line above, I get a compilation error when I hit the view:</p> <blockquote> <p>The type arguments for method '<code>...BaseViewModel.GetHtmlAttributes&lt;TModel,TProperty&gt; Expression&lt;System.Func&lt;TModel,TProperty&gt;)</code>' cannot be inferred from the usage. Try specifying the type arguments explicitly.</p> </blockquote> <p>I have to do the following:</p> <pre><code>&lt;%: Html.TextBoxFor(model =&gt; model.MyProperty, Model.GetHtmlAttributes &lt;ChildModel, string&gt;(model =&gt; model.MyProperty)) %&gt; </code></pre> <p>I'm just looking for some clarity as to how it tries to infer the type, it has no problem doing so in the <code>HtmlHelper/TextBoxFor</code> extension method? </p> <p>Is it because <code>HtmlHelper</code> in the view will automatically be for the same type as is specified in the <code>ViewUserControl</code> at the top of the page, whereas my code can be for any type inheriting from <code>BaseViewModel</code>? Is is possible to write this in such a way that it can infer my model/property types?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSteveC
    1. USVeli Gebrev
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POThe type arguments cannot be inferred from the usage. Try specifying the type arguments explicitly
      1. USuser75525
      1. VTFavorite
    2. VO
      singulars
      1. POThe type arguments cannot be inferred from the usage. Try specifying the type arguments explicitly
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POThe type arguments cannot be inferred from the usage. Try specifying the type arguments explicitly
      1. USTorbjörn Hansson
      1. VTFavorite
    1. COHoly horizontal scrollbars batman!
      singulars
      1. POThe type arguments cannot be inferred from the usage. Try specifying the type arguments explicitly
      1. USBen Lakey
    2. COYeah totally. It's absurd on our 30" monitors that we get just 6.5" for scrolling code back and forth in these tiny windows. Come on SA guys, take your VC money and get with dynamic page sizing!
      singulars
      1. POThe type arguments cannot be inferred from the usage. Try specifying the type arguments explicitly
      1. USSlaggg
 

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