Show Benefits in Code Analysis Details

By Michael Flanakin @ 3:42 PM :: 154 Views :: 0 Comments :: Visual Studio, (Open), (Unreported) :: Digg it!
I don't think the title I'm using is really getting the point across. What I'm really wanting is for the details behind code analysis warnings to let me view a report of a potential savings. This probably won't apply most of the time, but for something like the performance section, it's a huge deal. I want to know how much the corresponding change will benefit me. The reason this came to mind is because I'm working thru a group of projects that have around 15,000 code analysis messages -- yeah, it sucks. Well, I may or may not get thru them all, but the performance issues are the most important. Because of this, I'd really like to know exactly how each individual change may affect the system. Granted, I'm willing to accept the fact that the results may vary, but give me a general idea. Most of the perf changes I've seen will be of minor benefit... well, that's my logical determination based on the limited knowledge I have of the CLR inner-workings. I'd like to see an assessment of which changes will be most valuable and start with those. That information would be invaluable in a situation like this.

Ratings

Comments

Currently, there are no comments. Be the first to post one!
Click here to post a comment



Archives Archives

Categories Categories

Related Links Related Links