Get started for free
>
>

.NET Reflector Visual Studio Extension

VSIP Partner Trial

Integrates .NET Reflector into Visual Studio to allow you to seamlessly debug into third-party code and assemblies, even if you don't have the source code for them. Visit www.reflector.net for more information. Copyright (c) 2009-2013 Red Gate Software Inc.

(14) Review
Visual Studio
2012, 2010
Download (83,433)
2/19/2013
8.0.2.313
View
E-mail Twitter del.icio.us Digg Facebook
Add To Favorites
Description
Reviews (14)
Q and A (2)
Sign in to Write a Review
Sort By:

by Carsten Siemens | April 27 2013

A great tool!

by Waqas M | February 08 2013

Good tool

by Peng C | February 07 2013

.NET Reflector Visual Studio Extension v7.0 or later installed, Visual studio 2010 SP1 often no response

by offler666 | January 25 2013

I liked the tool as it was a free one by Lutz Roeder. Nowadays I would not pay for It, as the benefit to free tools (JustDecompile, CodeReflect, ...) is to marginal for me.

by Mads Kristensen | November 28 2012

by BobT36 | September 28 2012

Wow I knew you could de-compile .dlls and things to an extent, as in get a basic list of the procedure calls and references, but the depth of this blows my mind. Never thought you'd be able to de-compile and see the EXACT code right there. Granted it isn't AS nice as working with it in your own solution, but wow it is certainly helpful to see what exactly is happening behind the scenes. Great for debugging 3rd party .dlls that just return a "No" when something's not working, and a godsend for retrieving some code from .exes where a dev hadn't backed up the source. Also nice to see how Microsoft does things when you're making calls to the framework components.

My only real grump so far is the tiny "Trial" notice at the top left of this page, there should really be a notice in bold at the top of the description that this is a 14 day trial, and you'll need to buy it for £120 at the website. Fantastic addon though.

by Đonny | September 20 2012

by veljkoz1 | August 21 2012

There are quite a few decompilers out there, but I think this is the only one that allows you to debug 3rd party dll's at runtime (given they aren't obfuscated...) - you can go step by step, step into, and everything else, just like it's your own code (it creates a debuggable clone of the assembly that enables this). This is very powerful option, but, having said that, it doesn't work quite nicely. The code it displays as "current execution line" isn't the one that's executed (like when you get when source code differs from debugging exe/pdb, when code is optimized etc), so you always have to look e.g. 7 lines above the currently displayed to see where he's at. Furthermore, it breaks in files where there's no break but it's breaking there just because they're calling the line in a file that has it. It's all minor issues, but mighty annoying at that... some assemblies might work without issue, mine haven't :)
All in all - an excellent decompiler, but that needs a few enhancements of the more advanced features.

by FranzVienna | July 26 2012

Since version 7.6 the installation for Visual Studio 2010 fails with the error message "The specified path, file name, or both are too long. The fully qualified file name must be less then 260 characters, and the directory name must be less than 248 characters."

Furthermore the menu items Tools>Visual Studio and Windows Integration (Ctrl+I) vanished.

Red Gate August 03 2012
| Edit |
Delete

Ah, yes - that's a broad issue that hits a few VS Extensions. We're aware of that error and working on get it cleared up.

And the integration options have been split (as of 7.6) to make sure there's no control inter-dependancy. The Windows integration function is now under Tools>Options, and the Visual Studio integration can be handled via the installer. If you're still having trouble with it, drop a note in the discussion tab and we'd be happy to help work it out.

by Ramana Nagineni | July 10 2012

Great tool to debug 3rd party dlls.

Red Gate July 11 2012
| Edit |
Delete

Really glad you like the tool, Ramana - thanks for the feedback!

by Dragan Radovac | May 16 2012

There's nothing not to like about this tool

Red Gate July 11 2012
| Edit |
Delete

Thanks, Dragan! Glad you like it.

by Ehsan Mohammadi | October 04 2011

it's The Best .net Decompiler tool!

Red Gate August 03 2012
| Edit |
Delete

Really glad you like the tool Ehsan! Have you tried the new release? There's some integration into VS2012 you might also enjoy :)

by Netizen K | August 26 2011

*

Red Gate August 03 2012
| Edit |
Delete

Hi Netizen - what didn't you like about Reflector back in August? If you want to start a discussion about it, we'd love to hear your feedback so that we can improve the tool.

by 0x49D1 | April 15 2010

Red Gate August 03 2012
| Edit |
Delete

Hi Nihi-l-ist (love the username) - glad you love the tool! Let us know if you have any feedback on the latest release - we'd love to know what you think.

Sign in to Start a Discussion

  • Reply to Discussion | Hide
    where are the release notes?
    2 Posts | Last Post February 20, 2013
    • Written February 20, 2013 
      Where are the release notes for v8.0.2.313 (and incidentally the earlier versions too)?

For obvious reasons, a link on this page to the release notes would be useful (not to mention professional).
    • Written February 20, 2013 
      You can find the release notes for version 8.0.2.313 on the page below:
http://www.red-gate.com/SupportCenter/Content/.NET_Reflector/articles/reflector-release-notes-8-x
There are also links to earlier version release notes on the page.
  • Reply to Discussion | Hide
    Invalid certificate and XP problems
    2 Posts | Last Post September 07, 2012
    • Written September 07, 2012 
      The current version cannot install on XP due to too-long-paths. It also says that the certificate is invalid but that could be a side-effect of the same problem.

FWIW it's possible to install the extension by renaming the .vsix to .zip, unpacking it and removing all the subfolders (only used for the certificate and signing info), then re-zipping and renaming back to .vsix.
    • Written September 07, 2012 
      That's pretty much the truth - Windows is still bound to MSDOS and its' 256-character file path limitation. NTFS supports up to 32,000 character filenames, but the path has to be in a special UNC format and most programs aren't aware of how to handle that style of path.

You may use your workaround or I hear there are some third-party solutions out there to intercept and prevent this sort of thing.