Call Hierarchy

Question

Hey guys,

My name is DJ and I'm the PM for the C# IDE.  One of the features we've been working on for this upcoming release is the Call Hierarchy, which allows you to explore the flow of code in your projects.  This walkthrough steps through the various ways that you can use the feature to understand relationships between methods, properties, constructors, etc. 

Given that this is one of the highly requested features for the IDE, we're excited to hear your feedback.  More specifically, it'd be great to hear your thoughts on the usability of the feature. 

For more information on the CTP itself, check out http://go.microsoft.com/fwlink/?LinkId=129231. 

Thanks!
DJ Park
C# IDE PM

---

Program Manager, Visual C#

Answer 1

I think this is great and I think it should be extended to the VSTS DB Pro dependency hierarchy as well.  This should be fairly straightforward for SqlDataSources that use Stored Procedures or even adhoc SQL statements (to list what tables your page is dependent on).  I think it could be extended to Linq to SQL, Linq to Entities as well.  All the info is there.

What would really be fantastic would be if this reference building system could be extendable.  For instance, we have a Database class that all our business logic  DB calls pass through and it has .StoredProcedure and .Sql properties.  Any literal strings set for those (and we use all literal strings) could be mapped to the Sql code Db Pro layer as well.

Answer 2

DJ,

Could you expand your explanation of the Call Hierarchy feature in terms of similar features in Red Gate's Reflector (Used/Uses/Derives) or Wesner Moise's NStatic (graphical flow tracing, static analysis)?

Thanks.