How can we improve WCF?

Easier way of doing dependency injection (alternative to IInstanceProvider derivations)

Even though WCF Web Api is now renamed to ASP.NET Web Api, the model on how to do dependency injection should be adopted by WCF as well.

119 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Lars Wilhelmsen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Password icon
Signed in as (Sign out)
  • Adminericam (Admin, Microsoft ASP.NET Future Feature Feedback) commented  ·   ·  Flag as inappropriate

    At this point of time there are several 3rd party Nuget packages released that accomplish WCF dependency injection where no default constructors are required (such as Ninject.Extensions.Wcf, Unity.WCF, Autofac.WCF, Castle.WcfIntegrationFacility, etc). There are no plans for WCF to incorporate this functionality directly in the .NET Framework.

  • G4rce commented  ·   ·  Flag as inappropriate

    Cant agree more.
    I hate creating Behaviors, attributes, IExtensibleObject<T> + the provider classes to extend WCF.

  • Sławek commented  ·   ·  Flag as inappropriate

    Move ASP.NET MVC dependency injection/common service locator to BCL and use them in all libraries

  • Ido Flatow commented  ·   ·  Flag as inappropriate

    +1, and also adding the need for better testable environment - we should be able to test the output message without needing to write inspectors

Feedback and Knowledge Base