Red Gate forums: .NET Reflector 7.0 Feedback

Show line numbers?

GeorgeR — Mon, 01 Apr 2013 03:02:01 GMT

I would love to be able to see the line numbers in the Disassembly window. Unlike Visual Studio, MonoDevelop and Unity3d don't have a direct connection to Reflector so it can't jump to an offending line automatically.

I don't particularly enjoy counting them either.

Reflector is crashing Visual Studio 2012

dkent600 — Fri, 22 Feb 2013 14:56:35 GMT

Hey, the Reflector Visual Studio extension is repeatedly crashing Visual Studio 2012 for me. I have finally disabled the extension. It seems to happen in association with loading and unloading projects using TFS to revert project changes or to unshelve project changes.

visual studio 2012 hangs on spash screen after install

sirkirby — Thu, 03 Jan 2013 20:29:44 GMT

I was no longer able to start visual studio after installing the latest v7.7 version of the vs 2012 reflector extension. Once i removed it, vs loaded normally.

I'm running windows 8 pro x64 and have several other vs addons installed as well. Anyone had this issue?

bug with phalanger

proff — Mon, 17 Dec 2012 11:43:58 GMT

il code:

Code:

.maxstack 5
L_0000: ldarg.1
L_0001: ldstr "SirenaAnnulPNR"
L_0006: stfld string [PhpNetCore]PHP.Core.PhpStack::CalleeName
L_000b: ldarg.1
L_000c: ldfld class [PhpNetCore]PHP.Core.ScriptContext [PhpNetCore]PHP.Core.PhpStack::Context
L_0011: ldarg.1
L_0012: ldc.i4.1
L_0013: call instance object [PhpNetCore]PHP.Core.PhpStack::PeekValue(int32)
L_0018: ldarg.1
L_0019: ldc.i4.2
L_001a: call instance object [PhpNetCore]PHP.Core.PhpStack::PeekValueOptional(int32)
L_001f: ldarg.1
L_0020: ldc.i4.3
L_0021: call instance object [PhpNetCore]PHP.Core.PhpStack::PeekValueOptional(int32)
L_0026: ldarg.1
L_0027: call instance void [PhpNetCore]PHP.Core.PhpStack::RemoveFrame()
L_002c: call object <sections/avia/bron/functions_sirena.php>.<Script>::SirenaAnnulPNR(class [PhpNetCore]PHP.Core.ScriptContext, object, object, object)
L_0031: ret

RemoveFrame called after PeekValue*
c# code:

Code:

stack.CalleeName = "SirenaAnnulPNR";
stack.RemoveFrame();
return SirenaAnnulPNR(stack.Context, stack.PeekValue(1), stack.PeekValueOptional(2), stack.PeekValueOptional(3));

RemoveFrame called before PeekValue*

RE: Cannot Install Reflector 7.6 VS2010 Extension On Windows XP

GabrielNar — Tue, 13 Nov 2012 13:38:40 GMT

This a frequent problem,that generally causes the long folder path in your device.(longer than 255 characters)
There's a lot of additional software on the internet which can help you.I found Long Part Tool.It helped me.
http://PathTooDeep.com
All you need to do is to download this program online and save all the settings to your computer. This program is compatible with Windows NT, 2000, XP, Vista and Windows 7. Create an icon for the Long Path Tool on your desktop for easy access. Each time you would like to manage files that have a long filename all you need to do is to click the icon and it will instantly direct you to a window that presents all your files. Here you can rename, delete, open and move your files instantly without the worries of error messages saying that there is some sort of a problem.

You may see the error "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters," under the following circumstances:
Opening an assembly with .NET Reflector
Exporting source code for an assembly using an add-in such as FileDisassembler, or FileGenerator
I hope that it will help you!
Good luck!
Cheers!

Access violation reading location 0x00000001; VS fatal crash

jakub misek — Wed, 17 Oct 2012 18:24:51 GMT

I have installed Reflector integration (VS12). After opening a project (not C# but another project types, or empty solutions with attached processes etc..), Visual Studio crashes. I was able to attach to devenv.exe and obtain memory dump.

Call stack:

Code:

Unhandled exception at 0x772715de in devenv.exe: 0xC0000005: Access violation reading location 0x00000001
... ... ...
kernel32.dll!750714dd()
ole32.dll!74fac8e2()
ole32.dll!74ea98ad()
[Managed to Native Transition]
[Native to Managed Transition]
[Managed to Native Transition]
RedGate.Reflector.VsPackage.dll!..() + 0x112 bytes
RedGate.Reflector.VsPackage.dll!..ProcessProjectReferences(EnvDTE.Project project, System.Action<RedGate.Reflector.VsPackage.Engine.AssemblyReference,RedGate.Reflector.Tools.ProcessorArchitecture> action, RedGate.Reflector.VsPackage.Engine.ProcessProjectReferencesOptions options, System.Action<string> failedToResolveAction) + 0x359 bytes
RedGate.Reflector.VsPackage.dll!...() + 0x46 bytes
RedGate.Reflector.VsPackage.dll!..() + 0x6f bytes
RedGate.Reflector.VsPackage.dll!..(System.Action<RedGate.Reflector.VsPackage.Engine.AssemblyReference,RedGate.Reflector.Tools.ProcessorArchitecture> action, System.Action<string> failedToResolveAction) + 0x6c bytes
RedGate.Reflector.VsPackage.dll!..(out bool someReferencesUnresolved) + 0x1c8 bytes
RedGate.Reflector.VsPackage.dll!..GetDirectlyReferencedAssemblies(out bool unReferencedAssemblies) + 0x16a bytes
RedGate.Reflector.VsPackage.dll!RedGate.Reflector.VsPackage.Gui.RobToolWindow.(out bool missingReferences) + 0x14f bytes
RedGate.Reflector.VsPackage.dll!RedGate.Reflector.VsPackage.Gui.RobToolWindow..() + 0x2f bytes
RedGate.Reflector.VsPackage.dll!?..() + 0x2f bytes
RedGate.Reflector.VsPackage.dll!?..() + 0x53 bytes
RedGate.Reflector.VsPackage.dll!RedGate.Reflector.VsPackage.Gui.RobToolWindow.() + 0xb0 bytes
RedGate.Reflector.VsPackage.dll!..() + 0x142 bytes

Due to obfuscation, I was not able to look onto last managed method on the stack, but I can provide locals of ProcessProjectReferences method ... or whole memory dump if anybody is interested ...

Do you have any hints, what can cause crashing like this? It seams reflector is reading project configuration properties here.

EDIT: I think, it crashes if the project does not have <PlatformTarget> property ...

RE: Cannot Install Reflector 7.6 VS2010 Extension On Windows XP

nick.maidment — Tue, 31 Jul 2012 15:36:52 GMT

This is a problem which has already been reported, see the following link for more details

http://forums.reflector.net/questions/2559/upgrade-to-760808-the-specified-path-file-name-or-both-are-too-long

Cannot Install Reflector 7.6 VS2010 Extension On Windows XP

martincostello — Tue, 31 Jul 2012 13:00:36 GMT

Attempting to install the VS 2010 Extension For Relector on my Windows XP machine fails.

Running the new installer just fails with the error code from Windows Installer of 1603.

Runnning the VSIX from the Visual Studio Gallery gives me the following.

Code:

31/07/2012 13:54:42 - Microsoft Visual Studio Extension Installer
31/07/2012 13:54:42 - -------------------------------------------
31/07/2012 13:54:42 - Initializing Install...
31/07/2012 13:54:42 - Extension Details...
31/07/2012 13:54:42 - Identifier : 04e215d3-4dfd-4ae4-b72c-d5ef91dc603b
31/07/2012 13:54:42 - Name : .NET Reflector Visual Studio Extension
31/07/2012 13:54:42 - Author : Red Gate Software Ltd
31/07/2012 13:54:42 - Version : 7.6.0.808
31/07/2012 13:54:42 - Description : 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-2012 Red Gate Software Inc.
31/07/2012 13:54:42 - Locale : en-US
31/07/2012 13:54:42 - MoreInfoURL : http://www.reflector.net/
31/07/2012 13:54:42 - InstalledByMSI : False
31/07/2012 13:54:42 - MinFramework : 4.0
31/07/2012 13:54:42 - MaxFramework : 4.0
31/07/2012 13:54:42 -
31/07/2012 13:54:42 - Supported Visual Studio Editions :
31/07/2012 13:54:42 -    Version : 10.0
31/07/2012 13:54:42 -       Ultimate
31/07/2012 13:54:42 -       Premium
31/07/2012 13:54:42 -       Pro
31/07/2012 13:54:42 -    Version : 11.0
31/07/2012 13:54:42 -       Ultimate
31/07/2012 13:54:42 -       Premium
31/07/2012 13:54:42 -       Pro
31/07/2012 13:54:42 -
31/07/2012 13:54:42 - Supported Isolated Shells :
31/07/2012 13:54:42 -
31/07/2012 13:54:42 - References :
31/07/2012 13:54:42 -    -------------------------------------------------------
31/07/2012 13:54:42 -    Identifier : Microsoft.VisualStudio.MPF
31/07/2012 13:54:42 -    Name : Visual Studio MPF
31/07/2012 13:54:42 -    MinVersion : 10.0
31/07/2012 13:54:42 -    MaxVersion :
31/07/2012 13:54:42 -    MoreInfoURL :
31/07/2012 13:54:42 -    Nested : No
31/07/2012 13:54:42 -
31/07/2012 13:54:42 -
31/07/2012 13:54:42 - Searching for applicable products...
31/07/2012 13:54:42 - Found installed product - Microsoft Visual Studio 2010 Ultimate
31/07/2012 13:54:42 - The extension with ID '04e215d3-4dfd-4ae4-b72c-d5ef91dc603b' is not installed to Microsoft Visual Studio 2010 Ultimate.
31/07/2012 13:54:42 - Found installed product - Microsoft Visual Studio 2010 Premium
31/07/2012 13:55:42 - The following target products have been selected...
31/07/2012 13:55:42 - Microsoft Visual Studio 2010 Ultimate
31/07/2012 13:55:42 -
31/07/2012 13:55:42 - Beginning to install extension to Microsoft Visual Studio 2010 Ultimate...
31/07/2012 13:55:42 - Install Error : System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.BeginInstall(IInstallableExtension installableExtension, Boolean perMachine, AsyncOperation asyncOp)
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallWorker(IInstallableExtension extension, Boolean perMachine, AsyncOperation asyncOp)

It appears that the user data folder being generated for the installation path is too long for Windows XP machines. The path displayed in the installer is shown below, and appears to be truncated.

"C:\Documents and Settings\XXXXXXXXX\Local Settings\Application Data\Red Gate\.NET Reflector\Visual Studio Extension Inst"

RE: Odd Constructor Initializer

billrob458 — Tue, 29 May 2012 12:54:04 GMT

Thanks for the reply Nick. I figured as much that all the logic was inlined. I was hoping there was some special trick we could use to have more complex "default" parameters we could pass to a constructor initializer.

RE: Odd Constructor Initializer

nick.maidment — Tue, 29 May 2012 07:44:44 GMT

The code Reflector is generating is incorrect. It is trying to do the equivalent of the following, which does compile.

public Program(Func<string>x)
{
}

public Program(string errorMessage)
: this(() => errorMessage)
{
}

Ie the stuff to do with the local variable func, is supposed to be happening inside the call to this(�)

By the way, we also have a newer forum here: http://forums.reflector.net/

Odd Constructor Initializer

billrob458 — Tue, 29 May 2012 03:32:36 GMT

This might just be a fluke of the C# disassembler. I'm looking at the ValidationAttribute class of the System.ComponentModel.DataAnnotations (v4).

The ctors look off. I'm pretty sure this is how the code is behaving as the late bound Func<string> around the message is clearly working.

How is "func" passed to the ctor initializer *before* it is declared.

Code:

protected ValidationAttribute(string errorMessage) : this(func)
{
Func<string> func = null;
if (func == null)
{
func = () => errorMessage;
}
}

It would be amazing if we could apply complex default logic to pass to ctor initializer.

I tried doing this and it doesn't compile.

Code:

public abstract class Adam
{
protected Adam(Func<bool> myFunc)
{

}

protected Adam()
   : this(func)
{
   Func<bool> func = null;

   if (func == null)
      func = () => true;
}

protected Adam(bool errorMessage)
   : this(func)
{
   Func<bool> func = null;
   if (func == null)
   {
      func = () => errorMessage;
   }
}
}

RE: CTRL+F brings Standard Windows Search & Replace Dialog

Bart Read — Mon, 16 Apr 2012 11:30:10 GMT

It's OK, it hasn't changed. The shortcut for Reflector's search, which you can find on the Tools menu, is F3. CTRL+F has always brought up the text search when the decompilation pane has input focus.

CTRL+F brings Standard Windows Search & Replace Dialog

Cracker — Mon, 16 Apr 2012 09:06:00 GMT

Hi ,

When i press CTRL+F in Reflector window, "Standard" Search / Replace Dialog pop-ups instead of Reflector's own one.
I don't know when and how it's changed. But i can't restore it.
How to restore it? Please help me.

RE: How to NOT get into disassembly when 'go to definition'?

Clive Tong — Wed, 14 Mar 2012 08:21:51 GMT

Hi.

Discussion about the newer versions of Reflector have moved to the new forums, and there's already a post on the subject there: http://forums.reflector.net/questions/363/restore-f12-go-to-definition-for-vs

How to NOT get into disassembly when 'go to definition'?

samid — Tue, 13 Mar 2012 22:15:39 GMT

Hi,

I have .NET Reflector 7 VSPro installed (as part of the development bundle). Now when I press F12 or select 'Go to definition' in Visual Stuidio's context menu on a member, I get to the code disassembled by Reflector. OTOH, if I select "Go to decompiled definition" (which sounds like it should do what F12 does instead) - nothing at all happens.

So I actually have two related questions:

- how can I revert to the Studio's old behavior when pressing F12, i.e. go to the property definition AND DESCRIPTION and not to the disassembled code?

- how can I fix the new (added by Reflector) context menu so that IT DOES go to the disassembled code (which is useful sometimes but not always as I often just want to see the help)?

Thanks.