The project team is using TFs for collaborative development. Due to the large number of people, in the first place, to ensure normal development, the project team opened code analysis and forced the check-in policy for code analysis. After a project is compiled for a period of time, an error "ca0503: Unable to display additional code analysis warnings or errors" is generated every time ", but there is a red error, and it is always uncomfortable, and the compilation speed becomes very slow.
I found a lot of information and found out that it took too much time for code analysis, and the error prompt was also because the number of warnings or errors found during code analysis has exceeded the limit,. Because the project can be generated smoothly at the end, there are not many project errors, but too many warnings. How can we solve these two problems?
A simple method is to modify the limit value of the warning in the path below the registry. HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ visualstudio \ 8.0 \ Setup \ EDEV \ codeanalysiserrorlistviolationlimit. The default value is 200. You can modify it as long as the value is greater than the warning value of your compilation project, the above error will not occur, but do not increase the value without limit, because the cost of code analysis is increased. Since a large number of warnings are generally invalid, controlling this value will help improve the efficiency of solution compilation and generation, saving you time.
In addition, one solution is to minimize the number of code analysis items for each project. Because of a large number of warnings, we will ignore them, but will overwhelm the warnings we should pay attention, therefore, I suggest carefully selecting every major item in code analysis. This improves the code quality.
Another best solution is to strictly compile the code as required and eliminate all warnings.