BT
x Your opinion matters! Please fill in the InfoQ Survey about your reading habits!

ASP.NET Advanced Web Frameworks Gets Better with New Features, Bug Fixes and Improvements

by Anand Narayanaswamy on Jul 11, 2014 |

Microsoft has released new features, improvements and bug fixes to several advanced ASP.NET frameworks. ASP.NET MVC 5.2 brings in improved attribute routing with the help of IDirectRouteProvider extensibility point. It provides full control over how attribute routes are discovered and configured and is responsible for providing a list of actions and controllers along with associated route information.

The MVC framework provides support for message wrappers in ValidationMessage(), top-level elements in ValidationSummary() and HTML optgroup in DropDownList. It also fixes a bug where FormValueProvider does not recognize array item members from jQuery posts besides finding a way to support disable <option> or <optgroup> using SelectList.

Along with the latest release, ASP.NET product team has provided solutions for certain issues related to Scaffolding and installation failure of Microsoft.jQuery.Unobtrusive.Validation NuGet package besides providing a workaround to fix syntax highlighting while editing Razor views using Visual Studio editor.

Microsoft also updated ASP.NET Web API 2.2 with support for aliasing properties, enum, containment, singleton, functions in OData v4 protocol. It also supports integration of ODL UriParser besides ComplexTypeAttribute, AssociationAttribute, TimesTampAttribute and ConcurrencyCheckAttribute support in ODataConventionModelBuilder.

The latest release of Web API provides an ability to supply friendly Title for actions in addition to support for parameter aliases for function calls, cast() function in $filter, open complex type in addition to camel case naming convention. It also provides support for attribute routing and OData Core Libraries 6.4.0 besides client support for Windows Phone 8.1 that enable developers to apply Web API Client NuGet package to implement client logic.

In case of ASP.NET WebPages, Microsoft has fixed an error which occurs on the JavaScript variable assignment line by prefixing every line inside the Razor block with @:. It also
added a feature by making TypeHelper.ObjectToDictionary(routeValues) public and hence you can make use of new RouteValueDictionary(object) in your source code.

Microsoft has also announced that it will release a new Facebook package, Microsoft.AspNet.Facebook 1.0.0 to fix the existing broken package due to certain API changes made by Facebook. The Web API 2.2 framework doesn't include fixes to overloaded functions, string literals with URL encoded slash (%2F), backslash(%5C) and model binding of complex type when attribute routing is used. However, Microsoft has provided the required workaround to fix the above mentioned issues.

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Educational Content

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2014 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT