Decompiling to IL

Hi,

I quite like the new decompiling feature, specially because it is such a seamless experience. It would be nice to have a way to navigate to IL instead of to code? This is definitely a nice to have but it would be useful in certain cases. In case it is not clear, I would mainly be interested in navigating to the IL of my code.

I am quite happy with the improvements in 6.0 more specifically with the treatment of strings (as in string.format) and in several other details that together contribute to a better coding experience. This EAP also seems to be more stable than the latest one. Congratulations!

Finally, I don't see any difference in terms of performance (when compared to 5.1.x I was using before) but it has never been too bad for me and it is usable in a 25+ projects solution (WPF application). The worst I have is whenever I recompile the whole solution I get a delay of maybe two seconds when I Ctrl+tab from a  cs file to a xaml file. This delay goes down to maybe half a second subsequently.

Cheers,
Jose

2 comments
Comment actions Permalink

Hello Jose,

Thank you for feedback! We're considering decompilation to IL, but at the
moment it is not planned for the nearest future.

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi,

I quite like the new decompiling feature, specially because it is such
a seamless experience. It would be nice to have a way to navigate to
IL instead of to code? This is definitely a nice to have but it would
be useful in certain cases. In case it is not clear, I would mainly be
interested in navigating to the IL of my code.

I am quite happy with the improvements in 6.0 more specifically with
the treatment of strings (as in string.format) and in several other
details that together contribute to a better coding experience. This
EAP also seems to be more stable than the latest one. Congratulations!

Finally, I don't see any difference in terms of performance (when
compared to 5.1.x I was using before) but it has never been too bad
for me and it is usable in a 25+ projects solution (WPF application).
The worst I have is whenever I recompile the whole solution I get a
delay of maybe two seconds when I Ctrl+tab from a  cs file to a xaml
file. This delay goes down to maybe half a second subsequently.

Cheers,
Jose
---
Original message URL:
http://devnet.jetbrains.net/message/5297806#5297806



0
Comment actions Permalink

I'd like to put a different spin on this request.  Rather than having an option to "Navigate to IL", I suggest adding a new "Member IL" window which displays the IL bytecode for the "current member".  When the Object Browser is active, the "current member" would sync with the member selected within Object Browser.  When a code document belonging to the current solution is active, the "current member" would sync with the member whose definition contains the editor caret.  If the caret is within a type definition but not within a member definition, the view could default to showing the .ctor/field initializers.  If the displayed IL is no longer valid (due to code changes since the last compile), then the opacity could be adjusted to indicate the IL is out of date.  If the project has never been compiled (or has been cleaned), the window could display a message indicating that the project must be built before the IL can be displayed.

Such a feature would be useful for analyzing the IL being generated by the compiler.  When writing performance-critical code, it would be very convenient to see what the compiler is actually emitting without having to switch over to Reflector to analyze the build output.

0

Please sign in to leave a comment.