IIS 500.19 error Resolution process logging

The previous period of time has been tangled in C #, DLL management issues. Finally choose to use Nugetgallery for Public Library management. Project address: Https://github.com/NuGet/NuGetGallery. This is the server side of NuGet.

There is nothing wrong with the whole compilation. But when you publish to IIS, you are prompted:

HTTP Error 500.19-internal Server error cannot access the requested page because the associated configuration data for the page is invalid. Detailed error message:

Module	IIS Web Core
Notice	Unknown
Processing program	Not yet determined
Error code	0x8007000d
Configuration error
Configuration file	\\?\e:\website\nuget\web.config

The requested URL	http://localhost:80/
Physical path
Login method	Not yet determined
Logged in user	Not yet determined

Configuration Source:

See this first reaction is to find Niang. But the depressing is, all just say that the configuration file has errors, depending on the number of configuration lines prompted to find errors. But did not prompt to the specific error line ... After trying a variety of methods, still no solution, very helpless.
After a few days, and so busy work on the matter, and then back to continue to study the problem, but left the whole right is still no solution. Just when it's time to give up, the idea is: since there is a problem with the configuration file, I will go directly to the default empty configuration file without adding any additional configuration.
Then add the configuration one at a-until you are prompted for the error. The final location error is the node: System.webserver/rewrite. 100 degrees to know, this is the configuration of URL rewriting in IIS, Degree Niang also said that if you need to use URL rewriting, you need to install
Rewrite components. Well, after installing this component, the problem is resolved.
   Summarize:
     1 I have been troubled by this problem for many days. I hereby remember.
     2 Looking back at this problem, found that they are too dependent on the Niang, the first response to the problem is Baidu. Without a detailed analysis of the problem. Also, the configuration rollback, and then the method of troubleshooting to finally remember. A little sad. But fortunately, finally solved. So later encountered problems, should first analyze the problem, and then follow the analysis of the question to find the Niang.
If the degree of Niang can not tell me the answer. Then it should be reduced to a simple, each to find out the results.
     3 IIS This hint seems to be too pit point, direct hint unknown configuration is which not on the line, also mealy, error hints not in place

IIS 500.19 error Resolution process logging