aspnetcore/test/Microsoft.AspNet.Mvc.ViewFe.../ViewComponents
Doug Bunting d1fe824b5d Improve `SearchLocations` handling
- do not blindly use `FindPage()` / `FindView()` result in `Exception.Message` or returned results
  - failure scenarios involve new `Any()` calls but rarely additional `List<string>()` allocations
- change `ViewEngine_ViewNotFound` resource to be consistent with similar errors
  - remove trailing period at end of searched locations list

nit: remove remaining `null` checks of `SearchedLocations` in not found cases; never `null` then
2015-11-18 15:59:20 -08:00
..
ContentViewComponentResultTest.cs Allow ViewFeature tests to run in dnxcore50 2015-10-06 09:46:49 -07:00
DefaultViewComponentActivatorTests.cs
DefaultViewComponentDescriptorProviderTest.cs Allow ViewFeature tests to run in dnxcore50 2015-10-06 09:46:49 -07:00
DefaultViewComponentSelectorTest.cs Allow ViewFeature tests to run in dnxcore50 2015-10-06 09:46:49 -07:00
JsonViewComponentResultTest.cs Allow ViewFeature tests to run in dnxcore50 2015-10-06 09:46:49 -07:00
ViewComponentConventionsTest.cs
ViewComponentMethodSelectorTest.cs Use Type.GetMethod in ViewComponentMethodSelector 2015-10-06 16:21:56 -07:00
ViewViewComponentResultTest.cs Improve `SearchLocations` handling 2015-11-18 15:59:20 -08:00