Currently the XML serialisers both output namespaces that are not required:
I'm not sure about the Data Contract serializer, but it is not difficult to supress these...
Just pass into the Serialize method an XmlSerializerNamespaces:
var xmlSerializerNamespaces = new XmlSerializerNamespaces();
var xmlSerializer = new XmlSerializer(objectType);
xmlSerializer.Serialize(xmlWriter, toBeSerialised, xmlSerializerNamespaces);
Where defaultNamespace could be set on the GlobalConfiguration.Configuration.Formatters.XmlFormatter or it could be read from the XmlRoot attribute (if present) on the object being serialised.34 votes
We are looking at exposes settings to control this behavior on the XML formatter
There is no way to forecast the execution order of WebApi Action Filters. It changes randomly each time the code is changed. It would be nice to have an integer property to control the order like in normal Mvc controllers, but also respecting the order they are put on the action method would be acceptable273 votes
Support for filter ordering is tracked on our CodePlex site here: https://aspnetwebstack.codeplex.com/workitem/1065. Please add your vote to the CodePlex issue if you care about this feature!
Support for JSONP is being tracked on our CodePlex project here: https://aspnetwebstack.codeplex.com/workitem/1157. Please add your vote to the CodePlex issue if this feature is important to you!
I think maintaining and working with ASP.NET MVC and ASP.NET Web API side by side in the same project is a drain on development resources and support cost.
I would like to use ASP.NET Web API to generate Razor views via an additional NuGet package rather then relying on ASP.NET MVC.57 votes
We plan to do work to better align ASP.NET MVC and Web API in our next release
- Don't see your idea?