WCF (Web Services)
-
Implement EXI encoding
Implement standard based binary encoding for xml to enable much smaller wire size.
4 votes -
Proxy Generation with more features and large data transfers handling with more extensibility points.
During the proxy generation, give more features such as instance management and throttling options on User interface instead of handling in our own instance of proxy(such as checkboxes for applying those attributes). Also give methods in the proxy generated that if larger than a specific size, be handled in batches by default synch or Asynch which can be overridden if required.Can there be more extensibility points so that we can look at the message transfer more deeply on the transport level if required to check like how many batches are transferred and how many are remaining. And what about Known…
7 votes -
Better Timeout Exception Logging
If you've worked with WCF for any amount of time you've no doubt had to pour through trace files and then try to decipher exactly what timeout setting was causing a particular transaction to fail.
The exceptions thrown by WCF should provide much more concise information- such that it shouldn't be necessary to enable tracing and pour through logfiles to determine the root cause of a particular failure.
4 votes -
Make WCF endpoint and other settings brain dead easy and foolproof.
Getting WCF configuration settings right is unnecessarily difficult. Fix it once and for all otherwise this hinders wider adoption of WCF.
89 votes -
859 votes
-
OperationContractAttribute.WrapperNamespace
Two reasons:
1. If two services are created under the same xml namespace and they both have an operation with the same name then two types with the same FULLY QUALIFIED NAME would be declared.
I imagine that the default behavior cannot be changed but at least give us a way to change it.
2. In order to avoid the above issue some teams create message types on a different namespace altogether. The current implementation forces the client to use MessageContracts when a simple WrapperNamespace property would solve this and simplify life for many developers.1 vote -
Do not obsolete WebHttpEndpoint in favour of ASP.NET web api.
When I'm writing REST services I don't want to have ASP.NET around. I'd like to use a single service-oriented framework (WCF) to create both REST and SOAP services. The advantages of using a single service-oriented framework outweigh funky/shiny things of ASP.NET web api which I will never use. ASP.NET web api has moved away from service orientation concepts (unfortunately), but WCF should still be capable of supporting REST services.
11 votes -
Real contract first
WCF should allow implementing SOAP services with contract first, meaning WSDL & XSD. Xml Serializer needs to be able to understand Xml Schema standard better (e.g. maxOccurs, minOccurs, etc) and allow exposing the initial schema instead of generating schema from code in runtime.
43 votes -
Create a constructor on Host and Proxies that can read the WCF service config from a stream
It would be nice in clustered scenarios if the WCF config could be stored in a common location (Database, MEX web service, shared file) and then initiated from the host via a constructor. Right now it's very difficult to actually dynamically change the configuration without either subclassing the objects and hacking the dynamic config in or having to write your own parser for the config when there are obviously classes that do this already in the current system.
12 votes -
Remove the massive silent exceptions in WCF
At the moment it is not possible to turn on exceptions in the debugger because there are so many thrown and catched exceptions in WCF.
91 votes -
Make all WCF bindings IQueryable
Make all WCF bindings IQueryable as WebAPI
117 votes -
5 votes
-
Small web server using WCF
Host web client (may be ASP.NET enabled) in standalone application or service near or using WCF.
3 votes -
Implement full support for Username Token Profile 1.0 and 1.1
Current WCF implementation supports only PasswordText mode from Username token profile 1.0. Provide out-of-the box implementation for PasswordDigest which is very commonly used on other platforms (and was also supported in WSE) and also UsernameToken for key derivation defined in Username in Username token profile 1.1.
3 votes -
Xml schema validator
Current XML validation doesn't follow the Xml Schema standard and it's not possible to validate incoming messages against a schema. .Net framework really needs a proper Xml schema validator which can validate xml messages and also compare two schema versions to check breaking changes.
10 votes -
41 votes
-
Publish documentation of the JSON endpoints created from a WCF domain source.
Publish documentation of the JSON endpoints created from a WCF domain source. Trying to produce a javascript application using WCF on the server is next to impossible without knowing what the endpoints are. We need to know the endpoint signatures and how to build changeSets to talk to them.
32 votes -
Exception Marshaling out of box
Provide ability to exception marshaling in WCF vNext
30 votes -
Better Logging for non-XML messages
When using diagnostic tracing all messages appear as XML in traces even if they are transmitted / receieved in non XML format, e.g. JSON. I believe being able to log the actual bytes sent and received from the diagnostic traces and programmatically from a logging extensibility point would be a good improvement.
19 votes -
DataServiceContext 'accept: application/json' support
To reduce the data that is received by the client it would be great that DataServiceContext supports the json format as described by the OData protocol description: http://www.odata.org/developers/protocols/json-format
16 votes
- Don't see your idea?
