WCF 4.5: the configuration file is smaller, providing better support for ASP. NET.

Ido Flatow recently released an articleArticle, Which describes a series of changes that will be made in. Net 4.5.

As noise is reduced, the configuration file automatically generated by WCF is greatly reduced. Since the first version of WCF, developers have found that they need to maintain nearly 30 app. config files, which are actually the default values. People who know about configuration files will delete redundant settings. Unfortunately, many people have not learned this technique. With WCF 4.5, only the binding type and name are available in the configuration file by default.

Of course, this will lead to related training questions. "How do I know what the settings are ?" To answer this question, we will also see message prompts and auto-completion functions in the configuration file. This is not just a schema-based prompt; if you are configuring a terminal, you need to configure the behavior or name, it will be very intelligent to list it for you. If the configuration item, contract type, or behavior name is misspelled, this may even include support for Compiler warnings.

There is also good news for those who directly use WSDL. WCF 4.5 now returns the complete WSDL in a separate request. Previously, it only included some WSDL and also needed to obtain a series of matching XSD files. To use this method, do you need to use it? Singlewsdl queries strings instead? Singlewsdl.

Although deploying WCF in Windows Services is completely acceptable, most developers will continue to use IIS at work. Why not? IIS provides built-in support for many features, such as identity authentication, status management, and process recovery. However, there are some restrictions that Microsoft is trying to solve in this model. For example, the current developer needs to configure which authentication method is supported in two places. If they accidentally forget sync, the service will stop running. WCF 4.5 allows developers to set the authentication method type to "inheritedfromhost", so that the service complies with the IIS method, thus avoiding such specific defects.

Unfortunately, this is only part of the correction. If multiple authentication types are enabled for IIS, the client only recognizes the first one. Client developers can override it to use another type, provided that they can find another method. Note that this is completely a problem with the client tool. WSDL lists all options.

The defect in WSDL lies in creating a URI for the HTTPS service port. From. Net 4.0, WCF has the option to automatically generate a port for each binding type (HTTP, TCP, etc. Unfortunately, https was not included that time, and this negligence will be corrected in. Net 4.5. Ido Flatow mentioned that the HTTPS version will send the machine name instead of the host name used to request the WSDL. This can cause problems when using the Web field.

Another drawback is that WCF uses stream data. Ori believes that,

When you deploy the WCF Service in IIS, even if you do not use ASP. net compatibility mode, which also occupies some asp. net pipeline, which is in the msdn article "WCF Service and ASP. net (you need to find the part about the postauthenticaterequest event ). There are ASP. NET design defects in. Net 4, which will cause the requests sent to WCF to be cached in ASP. NET. This cache behavior can cause many major side effects:

This will not only cause latency in processing requests, but also cause a very large amount of content to overflow into the hard disk. This will also be corrected in WCF 4.5.

View Original English text:Lighter configuration files and better ASP. NET support with WCF 4.5

Infoq: WCF 4.5: the configuration file is smaller and better support for ASP. NET