Code analysis messages against ASP.NET projects have greatly improved in the private drops I’m testing. One of the things that caught me off guard in the earlier builds was that some warnings and error messages had no associated file names or line numbers. Now that has been fixed, most violation messages do have this information, with the exception of some namespaces and types because the compilers do not generate .pdb information for these. Fortunately it is possible to search on the identifiers and resolve the violations that way. If you do have other experiences along these lines with the code analysis experience let me know so I can feed it back into the team.