aspnetcore/test
Doug Bunting ae4cafc002 Correct evaluation of expression result in `GenerateSelect()`
- #1468
- Always use `ModelExplorer` in `<select/>`, `DropDownListFor()` and `ListBoxFor()` cases
 - allows evaluation of more-complex expressions
- Use `ViewData.Model` in `DropDownList()` and `ListBox()` template cases
 - `ViewData` was previously ignored in these cases

nit: change `ViewDataDictionary.Eval()` to return `Model` if `expression` is `null` or empty
- now `throw` on `null` or empty `expression` name in `ViewDataEvaluator.Eval()`
- simplifies some of the higher-level code
 - no change to `selectList` fallback; `Model` incorrect for that case
 - no change to `GenerateRadioButton()`; would change behaviour unrelated to #1468
  - this helper uses incorrect `ViewData` lookup text, see #1487
2015-03-02 12:07:43 -08:00
..
Microsoft.AspNet.Mvc.Common.Test
Microsoft.AspNet.Mvc.Core.Test Correct evaluation of expression result in `GenerateSelect()` 2015-03-02 12:07:43 -08:00
Microsoft.AspNet.Mvc.FunctionalTests Update functional test: 2015-02-27 10:44:35 -08:00
Microsoft.AspNet.Mvc.ModelBinding.Test Follow up to `ModelExplorer` creation 2015-03-01 09:39:36 -08:00
Microsoft.AspNet.Mvc.Razor.Host.Test
Microsoft.AspNet.Mvc.Razor.Test
Microsoft.AspNet.Mvc.TagHelpers.Test Correct evaluation of expression result in `GenerateSelect()` 2015-03-02 12:07:43 -08:00
Microsoft.AspNet.Mvc.Test
Microsoft.AspNet.Mvc.WebApiCompatShimTest
Microsoft.AspNet.Mvc.Xml.Test
WebSites Reacting to hosting API changes 2015-03-02 12:03:01 -08:00