WCF (Web Services)

Announcement: This forum has been replaced by Visual Studio Developer Community to provide you one convenient and responsive system for all feedback. You can now suggest new ideas, browse and vote on existing ideas in the Visual Studio Developer Community.

We’d like your suggestions and ideas to help us continuously improve future releases of WCF Web Services, so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.

Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.

We look forward to hearing from you!
- The WCF Web Services Team

How can we improve WCF?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Improve webHttpBinding performance

    At the moment performance of raw IHttpModule as well as Asp.Net web API is way better than webHttpBinding endpoints. Rewriting all WCF stuff is not an option. Real optimization from MS is needed to keep WCF on top.

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Ability to skip operation and manually generate custom response

    A simple way to transition from IDispatchMessageInspector.AfterReceiveRequest directly into BeforeSendReply skipping the actual operation code and instead manually crafting a response message. This is required to handle preflighted POST requests in CORS and other scenarios.
    http://blogs.msdn.com/b/carlosfigueira/archive/2012/05/15/implementing-cors-support-in-wcf.aspx
    http://social.msdn.microsoft.com/Forums/eu/wcf/thread/55ef7692-25dc-4ece-9dde-9981c417c94a
    http://social.msdn.microsoft.com/Forums/nl/wcf/thread/251188b6-87ff-43c8-b6a3-cb77e7aa62e0

    5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Conditional serialization support

    Serialization of certain properties in a class is not always decided during compile time. Either the name or the fact if it is serialized at all can depend on different circumstances. I am thinking of a context based solution when the context is passed to the serializer during serialization and it can be used in the DataMember attributes in order to decide the serialization behavior of the property.

    DataMember<TContext>(Func<TContext, bool> isSerialized, Func<TContext, string> serializationName,... etc.]

    5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Better technology for REST services

    In fact, now we do not have convenient universal approach for REST services, platform looks fragmented and when you see any real application having WCF with Http binding, Data Services or Web Api, you realize that they all have serious disadvantages.

    WCF over HTTP implements just old good RPC over the web and client can use only features mentioned by server side developer, plus there are tons of boilerplate code for every small feature you could need.

    Data Services as of today is bad implementation of good idea - you can generate a service from EF model in 5 minutes,…

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Implement EXI encoding

    Implement standard based binary encoding for xml to enable much smaller wire size.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Make it easier to set the serialization type for an endpoint in the endpoint config alone

    I shouldn't need to decide if an operation's content is going to be serialized in XML or JSON when I'm adding it to the service contract. I should be able to specify this from the endpoint configuration alone.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. [.Net Framework 3.5]Support TLS 1.2 in WCF (net.tcp)

    The .Net Framework 3.5 SP1 can support TLS 1.2 with this KB (https://support.microsoft.com/en-us/kb/3154518), however the WCF is still using the default protocol (SSL 3.0/TLS 1.0), and there is no way to change it, so my question is how to suggest Microsoft Team to provide a KB for WCF to support TLS 1.2? Thank you.

    More background information: We are developing application in SharePoint 2010 which cannot use .Net Framework 4.x, so we still need to use .Net Framework 3.5.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Keep-alive for bindings/channels

    This is something that is implemented over and over again with different approaches and different combinations of settings. Channel timeouts are good, but the mechanism we use to keep them alive when things are good would be nice if that was an out-of-the-box feature.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Multiple Services under one session.

    I want to segregate my operation contracts into many service contracts. But still want to authenticate user once and allow him to consume other service contracts without asking credentials.

    If possible I would like to share some information between service contracts, just like ASP.NET session

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Source Code XML comments to/from WSDL Documentation

    (Hope I'm in the right place for this...)

    My WCF project is carefully documented with XML comments (///<summary> This method is for adding </summary ) but in order for clients to see this usage documentation, we both have to use an add-on package (WCF Extras) which requires a fair amount of web.config acrobatics. It would be nice if WCF had native support to turn those comments into "xs:documentation" elements in the WSDL on the server side and then read them back out on the client side.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. conditional datacontract serialization

    I would like to serialize my DataContract Object based on the conditional statements implemented inside the Datamembers

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Owin support

    Abstract WCF from IIS and follow suit with the rest of ASP.NET

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Run WCF on Linux

    Our customer need this.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Enhance the offical docs on each extensibility class and show how to instatiate and wire it into WCF

    WCF has some of the best extensibility I have ever seen in a complex software system, but it is VERY difficult to figure out how to actually instantiate your own version of some of the classes and get them wired into WCF correctly. Carlos Figueira's WCF Extensibility blog is awesome, but that is a narrative format, not a reference format. And his blog does not cover all wire up scenarios.

    For example, at this moment I an trying to figure out how to wire up my own version of a IDispatchMessageFormatter implementation. He mentions how to do this in his…

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Document 'under-the-covers' request-processing workflow when using WCF extesnsions.

    Document 'under-the-covers' request-processing workflow when using WCF extesnsions. Eg Gotchas in concurrent request handling scenarios (statics shared across contexts unexpecedly making life miserable for service developers )

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

WCF (Web Services)

Feedback and Knowledge Base