3 ms·
Couldn't they move to a more code and convention driven config system? I know what you mean, though. I have this one web service that's the bane of my existenc
by sudioStudio64 11y ago
Couldn't they move to a more code and convention driven config system?
I know what you mean, though. I have this one web service that's the bane of my existence. No WSDL, it's WS-Transfer and MEX and WS-Sec with it's own STS...makes me weep thinking about it.
- anton_gogolev 11y agoAgain, very unlikely. It will either be a godawful Fluent API on top of all the WCF craziness, or the conventions will be as unusable as they are in Entity Framework. Old-style ASMX services were cool. Nothing fancy, no infinitely configurable doodads: just a single class annotated with attributes.
- useerup 11y agoWCF does allow for code based configuration. There are actually 3 way to configure everything in WCF: Imperative code, Declarative attributes and (xml-based) config files. Conventions are supported as well, but is woefully underused. That said, WCF is a beast. If you need SOAP with federated security and bells and whistles, it is a very solid choice. If you can make it through with REST you should avoid WCF. It is a time sink.