By the end of first exercise , we can list through list of method calls in a particular method body. Now, my target will be to take a assemblyname::typename::method as input then recursively iterate through the method lists and generate a nice looking visualization. So, we redifine out parseMethodbody...

As I said in the last post, the output from Microsoft GLEE looked but not ideal and as the method tree gets bigger with more relationships, the diagram gets out of control. Disappointed with that, my further search takes me to the Netron Project, which is a diagramming and graph layout toolkit for Microsoft...

As I said in the last post, the output from Microsoft GLEE looked but not ideal and as the method tree gets bigger with more relationships, the diagram gets out of control. Disappointed with that, my further search takes me to the Netron Project, which is a diagramming and graph layout toolkit for Microsoft...

UPDATE: [ Part III with Netron Project ] By the end of first exercise , we can list through list of method calls in a particular method body. Now, my target will be to take a assemblyname::typename::method as input then recursively iterate through the method lists and generate a nice looking visualization...

Inspired by this post by Sam Gentile , I decided to play with Cecil . And this gives me another oppurtunity to use IronPython. The end result may not be very attractive but it has the potential :). >>Read more on Fun with IronPython and Cecil

Inspired by this post by Sam Gentile , I decided to play with Cecil . And this gives me another oppurtunity to use IronPython. The end result may not be very attractive but it has the potential :). >>Read more on Fun with IronPython and Cecil