ASP.NET MVC / Web API / Web Pages

Reviewed: v4.0 RTM (五月 21, 2013)

xyening — Tue, 21 May 2013 07:09:46 GMT

Rated 5 Stars (out of 5) - good good good

Reviewed: v4.0 RTM (五月 20, 2013)

SeonWater — Tue, 21 May 2013 01:46:20 GMT

Rated 5 Stars (out of 5) - I like it.

Created Issue: Validation - consider using FileExtensionsAttribute from System.ComponentModel.DataAnnotations [1059]

kenegozi — Mon, 20 May 2013 22:28:52 GMT

The said attribute is new in .net 4.5

We should consider obsoleting out own FileExtensions attribute if the new attribute can be made to work with instances of HttpPostedFileBase (it is currently only for strings)

Otherwise we could consider identifying cases of the .net attribute being set on HttpPostedFileBase properties, and somehow notify the developer about using the correct attribute instead.

Created Task: JQuery validation plugin - version upgrade [1058]

kenegozi — Mon, 20 May 2013 22:17:20 GMT

MVC currently bundles version 1.10 from September 2012, the latest is 1.11.1 from March 2013.

Created Issue: JQuery Validation plugin - include additional-methods file [1057]

kenegozi — Mon, 20 May 2013 22:14:09 GMT

The JQuery Validation plugin is normally bundled with a file named additional-methods.js that adds some more validation methods to the basic ones that are in the plugin.

Two of which, 'accept' (for validating mime-types on input[type=file]) and 'extension' for validating file extensions (again, on input[type=file]), have support within MVC in the form of validation attributes (FileExtensionsAttribute and AcceptAttribute)

Currently the templates provided does not include that additional file, hence out-of-the-box these validation attributes only apply on server-side.

A fix would be to either add the nuget-package for the additional methods into the template, or to update the JQuery.validation nuget package to always include the additional methods file.
The default Bundle for jquaeyval should be updated as well.

Commented Issue: FileExtensionsAttributeAdapter no longer works with jQuery validate [882]

kenegozi — Mon, 20 May 2013 21:51:52 GMT

The "Accept" rule in the latest version of jQuery Validate now expects a mime type to be specified, not a file extension.

A new "Extensions" rule has subsequently been added for this purpose.

Note that as of v1.90 both of the above rules are now available separately inside the "Additional Methods" download.
Comments: The solution: 1. FileExtensions attribute will evaluate to the 'extension' method of JQuery Validation, and Accept attribute will evaluate to the 'accept' method 2. If the 'extension' method is not present (using MVC5 with an older version of jquery validation) then the FileExtensions attribute would use the 'accept' method, and Accept attribute will be ignored on the client side altogether. Fixed in https://aspnetwebstack.codeplex.com/SourceControl/changeset/803b6de9af1b4e77f805071bd9e521687903681b

Edited Issue: FileExtensionsAttributeAdapter no longer works with jQuery validate [882]

kenegozi — Mon, 20 May 2013 21:51:52 GMT

Commented Issue: Empty SingleResult cannot be formatted by the ODataFormatter [1040]

kenegozi — Mon, 20 May 2013 21:49:36 GMT

public override SingleResult<Customer> GetCustomer(int key)
{
return SingleResult.Create(Enumerable.Empty<Customer>());
}
Comments: Returning a 404 response when SingleResult has an empty feed Fixed in https://aspnetwebstack.codeplex.com/SourceControl/changeset/3fd6562cad19160992429ce12f378cdfb03c16e2

Edited Issue: Empty SingleResult cannot be formatted by the ODataFormatter [1040]

kenegozi — Mon, 20 May 2013 21:49:36 GMT

public override SingleResult<Customer> GetCustomer(int key)
{
return SingleResult.Create(Enumerable.Empty<Customer>());
}

Source code checked in, #3fd6562cad19160992429ce12f378cdfb03c16e2

Ken Egozi — Mon, 20 May 2013 21:45:00 GMT

#1040 Empty SingleResult action should return 404

Created Unassigned: Document that IValueProvider.GetValue() returns null if the exact key is not found [1056]

binki — Mon, 20 May 2013 21:25:26 GMT

Document that IValueProvider.GetValue() returns null if the exact key is not found.

Commented Issue: HelpPage not showing documentation for actions which have parameters as Nested types [905]

ejveal — Mon, 20 May 2013 20:00:58 GMT

From here:
[http://stackoverflow.com/questions/15410057/webapi-help-page-for-complex-type-in-uri](http://stackoverflow.com/questions/15410057/webapi-help-page-for-complex-type-in-uri)

Repro:
Copy the following class and enable Xml documentation on the project settings and also in HelPage's HelpPageConfig.cs
```
using System.Web.Http;

namespace MvcApplication31.Controllers
{
public class UsersController : ApiController
{
public class Preferences
{
public string Theme { get; set; }

public string Size { get; set; }
}

/// <summary>
/// Saves users' preferences
/// </summary>
/// <param name="pref">Preferences of the user</param>
public string SavePreferences(Preferences pref)
{
return "value";
}
}
}
```

Actual: "No Documentation Available"
Expected: comments specified for the action.

Comments: I'd like this fixed.

New Post: Web API OData - atom+xml formatting issue when getting individual properties

mkachala — Mon, 20 May 2013 06:58:26 GMT

Thank you!

That's what I wanted to know.

New Post: Web API OData - atom+xml formatting issue when getting individual properties

mkachala — Mon, 20 May 2013 06:58:26 GMT

Thank you!

That's what I wanted to know.

New Post: Web API OData - atom+xml formatting issue when getting individual properties

raghuramn — Sun, 19 May 2013 23:08:35 GMT

Complex properties are formatted as application/xml. Only entries and feeds (entities and collection of entities) are formatted as application/atom+xml. So, the behavior that you are seeing is correct.

You can get the behavior that you want by putting application/atom+xml and application/xml in the accept header like, "application/atom+xml,application/xml"

New Post: Web API OData - atom+xml formatting issue when getting individual properties

raghuramn — Sun, 19 May 2013 23:08:35 GMT

Source code checked in, #b3260efa7cd4b6382e7926fe9c600bb0e683bf69

raghuramn — Sun, 19 May 2013 22:51:41 GMT

[OData] Decrease max $expand depth to 1.

Reviewed: v4.0 RTM (五月 19, 2013)

legendpanda — Sun, 19 May 2013 13:57:34 GMT

Rated 5 Stars (out of 5) - thinks very much

Commented Issue: Make JsonContractResolver a public class [228]

CallMeLaNN — Sun, 19 May 2013 01:45:40 GMT

This would enable overriding the ResolvePropertyName method (see Newtonsoft.Json.Serialization.CamelCasePropertyNamesContractResolver) without having to reimplement the entire JsonContractResolver class. I would really like to keep its private property behavior.
Comments: Almost half day trying to understand how WebAPI serialize to JSON just because I want the first letter of JSON key lower case to standardize models in Javascript framework. At first I am stuck at Model Binder but after few hours I realize WebAPI uses MediaTypeFormatter to serialize/deserialize, then I found this. +1 to make it public, but it is really nice if camel case is applied in the JsonContractResolver by default.

Commented Feature: MVC Support Adding HTML Attributes to SelectListItems [9]

jlebright — Sat, 18 May 2013 14:06:55 GMT

I would like the ability to add Html attributes to individual SelectListItems via object htmlAttributes. This would be handy for applying CSS to selected options on render. I have working code for this (using the MVC3 source as the base) that I have used on client websites so it will be easy to integrate.
Comments: This is a great idea, but it can be even better with another overload that instead of just adding data attributes for every SelectListItem, consider adding a function as the parameter that can generate whatever parameter you want to based on the return value of the function. That way you can put together a nice lambda expression that returns a data attribute depending on the value or text of the SelectListItem.