Analyze Project

Real Studio has an Analyze Project function that scans your project for a variety of things and reports on them.  It checks for unused local variables, unused event parameters, and unused method parameters, to name a few.  It also checks for deprecated method calls in addition to checking for true compiler errors.

I hate to say it, but who cares?  Except for the deprecated methods check I don’t find many of these tests to be all that useful.  I checked with Seth and he doesn’t use it very often (he said rarely) either.  Are we being bad Real Studio developers?

Over the years I’ve worked on projects with outside developers.  Some of them are very vigilant (i.e. OCD) about analyzing their projects and, by golly, if there’s one single item in the list they have to get rid of it.  To me it’s over the top and, if not a huge waste of time, it’s not an efficient use of it.

Don’t get me wrong.  Knowing if you have unused local variables *IS* useful.  Deprecated items *IS* useful.  Unused event or method parameters?  Not so much.  I suppose there is *some* compiler advantages but it seems minor at best and certainly not worth the effort.

So my question for you, dear readers, is this:  Are you obsessive about Analyze Project?  Or do you even care?  If so, why is it so important to you?

Happy coding!