Edited Issue: Client side validation doesn't work for Number fields with...
When having a model that contains an property of type int. If you have an edit field where you introduce a non numeric value, like an 'a'. The jquery validation should be triggered, but it doesn't...
View ArticleClosed Issue: [AttributeRouting]Route not being added to route collection [1005]
__Note__: This behavior exists even in MVC attribute routing too. I haven't filed a new bug for it, but would like to use this bug.In the following scenario, the Get() action on ReproController, which...
View ArticleEdited Issue: Option to not encode TagBuilder attributes [895]
By default `TagBuilder` calls `HtmlAttributeEncode` on all attributes. Sometimes we do not want to encode our attribute values and `TagBuilder` does not provide a facility to do this. Either everything...
View ArticleClosed Issue: Provide consistent controller inheritance behaviors between MVC...
Currently there is a difference in how attribute based routes are generated between Web API and MVC in case of inheritance of controllers. Should we provide a consistent experience across both of...
View ArticleCommented Issue: Update MVC attribute routing to match latest design in...
Bring recent changes from WebAPI's attribute routing into MVC (e.g. removing HttpGet(route), and using the RouteCollectionRoute)Comments: Please consider...
View ArticleClosed Feature: MVC: Add RouteAttribute, remove attribute routing properties...
Merging attribute routing with the existing HttpXxxAttributes causes a couple of issues:* When using Web API conventions you end up repeating yourself on what HTTP verb is handled by the...
View ArticleCommented Issue: Update MVC attribute routing to match latest design in...
Bring recent changes from WebAPI's attribute routing into MVC (e.g. removing HttpGet(route), and using the RouteCollectionRoute)Comments: Please also consider...
View ArticleEdited Issue: Provide a way to filter requests to attribute routed...
Today it is cumbersome to use attribute routing with existing routes. For example, the default Web API route may route to a controller with attribute routes, which was probably not intended.We should...
View ArticleCommented Issue: Provide a way to filter requests to attribute routed...
Today it is cumbersome to use attribute routing with existing routes. For example, the default Web API route may route to a controller with attribute routes, which was probably not intended.We should...
View ArticleEdited Issue: Provide a way to filter requests to attribute routed...
Today it is cumbersome to use attribute routing with existing routes. For example, the default Web API route may route to a controller with attribute routes, which was probably not intended.We should...
View ArticleEdited Issue: Rename RouteName and RouteOrder properties to Name and Order...
The property names RouteName and RouteOrder are overly verbose now that they live on RouteAttribute.
View ArticleCommented Issue: Invalid names and ids are generated when the model type is...
If the view model type is a collection, then the names generated for it (using NameFor, IdFor etc.) are incorrect (for example, it might be generated as "Project.Employees.[0].Name" - note the extra...
View ArticleNew Post: OData Actions with Parameters broken in latest nightlies
Thanks TristanKazu for the repro...I took a look at this...looks like the problem is because of the type of return type that you are using when defining the OData action... Change the following...
View ArticleSource code checked in, #0de60c08a7c647d3a0d9e6af50db2c0ae14cede4
Consolidate DefaultRouteAttribute into RouteAttribute (fixes #1223).
View ArticleCreated Unassigned: OData actions do not work if the model has KeyValuePair....
1) Create a model having an ODataAction.2) Add a complex type KeyValuePair<string, object> to the model like this, model.ComplexType<KeyValuePair<string, object>>();3) Try accessing...
View ArticleNew Post: OData Actions with Parameters broken in latest nightlies
I have opened this bug to track this issue. https://aspnetwebstack.codeplex.com/workitem/1232
View ArticleEdited Issue: Remove HttpRouteBuilder [1229]
Currently the HttpRouteBuilder extensibility points in MVC and Web API are different and it looks like the abstraction needs some work. Let's remove HttpRouteBuilder, but keep IInlineConstraintResolver.
View ArticleCreated Unassigned: Request dispatched to incorrect action resulting in 400...
A request for '/api/customers' is resulting in 400 Bad Request. __Attached__ a katana selfhost repro.__Reason__:The problem seems to be happening because of the following piece of code in...
View ArticleEdited Unassigned: Request dispatched to incorrect action resulting in 400...
A request for '/api/customers' is resulting in 400 Bad Request. __Attached__ a katana selfhost repro.__Reason__:The problem seems to be happening because of the following piece of code in...
View ArticleEdited Issue: Request dispatched to incorrect action resulting in 400 Bad...
A request for '/api/customers' is resulting in 400 Bad Request. __Attached__ a katana selfhost repro.__Reason__:The problem seems to be happening because of the following piece of code in...
View Article