title: Identifying unused classes / controls / pages
body: <p>We have a 10+ years old ASP.NET website project, with lots of unused / legacy user controls and pages.</p>
  
  <p>Is there a tool which can assist in the process of identifying these elements of the solution, so we could refactor them out?</p>
  
  <p>I know the issue is complicated because not all types are referenced as types which a compiler / tool might recognize. e.g. objects instantiated by reflection are instantiated using a string representing the class name. In addition asp.net pages are generally not referenced as types, but as page identifier strings in markup.</p>
  
  <p>It still seems like someone would have created a tool which handles these cases and creates a candidate list of unused classes / pages / user controls</p>