Freigeben über

1 Question Survey on Configuration

  • Artikel

Since I did the survey question on extensibility, I thought I'd do this followup on configuration. The two are often talked about together but have very different needs.

Question:

What's the one thing you would change about how configuration is done for WCF applications?

Pick anything you want about the configuration format, tooling, integration with service code, or other topics as you'd like, but try to keep in mind that this is for an application that uses WCF. It's ok if the details of the change have to do with IIS or other products though.

Comments

  • Anonymous
    November 12, 2008
    The comment has been removed

  • Anonymous
    November 12, 2008
    Make it easy to avoid an Excel.exe.config file

  • Anonymous
    November 12, 2008
    This is almost like a feature ask for the standard .NET configuration system more than anything, but I definitley wouldn't complain if the WCF took it upon themselves to provide a custom way to do this... Enable the <system.serviceModel> and every custom section under that to be loaded from an external file rather than from the app/web.config itself. Meaning I'd like to be able to define some resuable custom bindings in a standalone file called MyCustomBindings.config and then be able to do something like: <bindings href="MyCustomBindings.config" /> Today I'd have either copy/paste across several .configs or write an actual binding of my own. Certainly I'd do the latter if I really was going to reuse it across many projects, but if I just want to share the bindings with my unit test project and my host application project I have to copy/paste today. This, in turn, leads to updates being made to one, but not the other and naturally you run into problems because what you tested isn't what you deployed. Cheers, Drew

  • Anonymous
    November 12, 2008
    The comment has been removed

  • Anonymous
    November 12, 2008
    Yes, external config files (so my class library can have its own .config file instead of making me put it in the parent).

  • Anonymous
    November 13, 2008
    Please make programmatic configuration provision and inspection easier. I'm mostly talking about self-hosted services now. I mean, would it be possible to a) provide a small set of classes specifically to do programmatic configuration, to make the code more readable :) For example, kind of Builder pattern when use give us some coarse bricks, from which we at first build the host "surface", and then ask them to build the ServiceHost instance and continue with additional tuning... b) provide API to dump host information without having to manually go through endpoints, channels etc. For instance, you could provide us with a kind of iterator class, which would go through all the elements of a given ServiceHost, giving a chance to dump/read specific information ourselves.

  • Anonymous
    November 13, 2008
    I would like something what MEF guys has done. Simple Imports and Exports in code ... though, it is not 100% possible in WCF, but something like this will add more easy way of configuring it

  • Anonymous
    November 13, 2008
    external files - I second that opinion. and provide a way to refresh the configuration at runtime. I know that there will be some limitations, but switching the trace level for example would be a nice feature.

  • Anonymous
    November 14, 2008
    A configuration "flow" is required for the SvcConfigEditor. For example when you choose to use "certificate" as the client authentication token then fields like "service expected spn identity" and "UsernamePasswordValidationMode" are irrelevant. "clientCertificate" on the other hand is required (although can be specified from code). Totally irrelevant fields should not appear - this is really confusing for people who are not web services experts.

  • Anonymous
    November 15, 2008
    The comment has been removed

  • Anonymous
    November 16, 2008
    The comment has been removed