Comments
3 comments
-
I second that! A Visual Studio add-in. I know a debug visualizer would not be that hard to do, although the functionality would still be useful at design-time.
When I worked on my duck typing project, I had to save the dynamically generated assembly so I could disassemble it with Reflector to troubleshoot errors. A debug visualizer would have avoided that step. -
Until they release a better one, you can try mine.
http://www.codeplex.com/NeovolveX/Release/ProjectReleases.aspx?ReleaseId=13336 -
I would like to throw my support as the number 1 requested feature I'd pay for. Specifically, I'd like to replace the Object Browser window.
Add comment
Please sign in to leave a comment.
It could really be helpful if you could highlight some code and then view it in, say, IL code, or some other code that perhaps you are more familiar with.
e.g. If I am looking at a VB project and I'm more of a C# developer and I don't understand what's going on exactly on a certain piece of code and I'm too lazy to look it up
I know this could be particularly difficult to do, but I would probably pay hundreds for it, and I bet I'm not the only one. This is what I use reflector primarily for now, but it can be tedious sometimes. This could really help break down the language barrier for a lot of developers, I think.