Conflict between WCF and IIS integrated Windows Authentication

I haven't been up for a long time. Recently, I jumped to a new company along with my old boss. I am working on a new dating project. Today I have finished my work. I would like to share a tips on WCF, as the project

In many cases, jquery + WCF is used to implement Ajax asynchronous data acquisition. In the development environment:

Directly in vs.net, right-click the SVC file to browse in the browser (the aspx server provided by vs.net is not used, but is set to use IIS directly in the project attribute), and the following error is prompted:

IIS specifies the authentication scheme "integratedwindowsauthentication, anonymous", but binding only supports one authentication specification. Valid authentication schemes are digest, negotiation, NTLM, basic or anonymous. Change the IIS settings so that only a single authentication scheme is used.

The error message is clear: IIS either uses integration verification or only anonymous authentication. Therefore, the integration verification check box in the IIS settings is removed. After IIS is restarted, it runs normally, but. net, but it cannot be used for breakpoint debugging (integration verification must be used to enable debugging). Is this the legendary "cannot have both fish and bear's paw "???

Unwilling to do so, in the IIS website, right-click the directory where SVC is located and check it. Haha, find the solution. IIS can allow separate directory (or virtual directory) set Directory Security, so the directory where SVC is located (all the WCF files in the project are concentrated in this directory) -- "Directory Security --> Removes the check box before integration verification, the whole site still adopts integrated verification. Now SVC can be viewed directly, while our silly vs.net can also be used for breakpoint debugging ...... (Yang Chao ^_^ under the bodhi tree)