Comments
Sort by recent activity
Hi.
Just to make it clear what Alex's tip does. If, for example, you compiled the following piece of code to MyApp.exe,
class Program
{
static void Main(string[] args)
{
Console.WriteLine("hello");
}
}
you'd end up with only private classes, so you couldn't navigate to the Main method via the object browser.
To stop on the first statement, you could set up MyApp.exe as the debug "start external program" in the properties of a new console application project. You could use the .NET Reflector "choose assemblies to decompile" menu item to bring up the dialog, and then browse to MyApp.exe and decompile it.
At that point, pressing F11 would step you to the first instruction of the decompiled code. For me, in a debug build, it stops on the first { of the Main method.
Stepping should then take you into private classes where you can set breakpoints once you have the source file loaded into Visual Studio. / comments
Hi.
Just to make it clear what Alex's tip does. If, for example, you compiled the following piece of code to MyApp.exe,
class Program
{
static void Main(string[] args)
{
Console.WriteLine("hello");...
Hi.
There are a couple of walkthroughs and demonstration videos here http://www.red-gate.com/supportcenter/Product.aspx?p=.NET%20Reflector which show the process.
When using Reflector Pro, you don't have to do any copying of sources from Reflector into Visual Studio. Visual Studio will be led by the debugging information that Reflector Pro generates to the de-compiled source code. / comments
Hi.
There are a couple of walkthroughs and demonstration videos here http://www.red-gate.com/supportcenter/Product.aspx?p=.NET%20Reflector which show the process.
When using Reflector Pro, you don'...
Thanks for bringing that to our attention. It’s now fixed. / comments
Thanks for bringing that to our attention. It’s now fixed.
Hi.
Taking the type System.Threading.SemaphoreFullException as an example, if I view the assembly information for System, in the disassembler pane I see
[assembly: TypeForwardedTo(typeof(SemaphoreFullException))]
and the hyperlinked SemaphoreFullException does take me to the new home for the type in mscorlib.
Are you suggesting that the type should also appear in the class/member selection pane so that if you expand the tree at the node System.Threading you'd see SemaphoreFullException next to the type Semaphore as you do when viewing the 2.0 libraries? This would mean that you can get to the destination type without having to go up to the assembly level. That sounds like a good idea to me and I'll log it. / comments
Hi.
Taking the type System.Threading.SemaphoreFullException as an example, if I view the assembly information for System, in the disassembler pane I see
[assembly: TypeForwardedTo(typeof(SemaphoreF...
> Would it be possible to get a copy of a build that has this optimization enabled?
Hi. The build that you have supports .NET 4 in the sense that you can browse .NET 4 assemblies. We haven't (yet) added support in Reflector for de-compiling to C# 4 or VB 10. / comments
> Would it be possible to get a copy of a build that has this optimization enabled?
Hi. The build that you have supports .NET 4 in the sense that you can browse .NET 4 assemblies. We haven't (yet) ...
Thank you for reporting this.
This is due to a change in behaviour of Assembly.LoadFrom in the framework, which is the method Reflector uses to load in the addin. .NET 4 is warning that the addin will no longer be executed in a sandbox.
The workaround is to modify the config file (Reflector.exe.config) to include the following element nested inside the <configuration> element.
<runtime>
<loadFromRemoteSources enabled="true" />
</runtime> / comments
Thank you for reporting this.
This is due to a change in behaviour of Assembly.LoadFrom in the framework, which is the method Reflector uses to load in the addin. .NET 4 is warning that the addin w...
Please see the reply in the ".NET Reflector Pro Beta" forum. / comments
Please see the reply in the ".NET Reflector Pro Beta" forum.
Thanks for the report.
We are running that version of Visual Studio here and haven't seen the problem. Please can you get us some more data about this problem by doing:
(i) Get rid of the add-in by starting Reflector, going to tools->integration options, unchecking all of the add-in check boxes and pressing ok.
(ii) Reinstall the addin by going to tools->integration options, checking the add-ins and pressing ok.
(iii) send the add-in definition file that gets created, (it's roughly 700k) which will be in the equivalent of
C:\Users\Administrator\Documents\Visual Studio 2010\Addins\RedGate.Reflector.Addin
to me at clive DOT tong @ red-gate.com. / comments
Thanks for the report.
We are running that version of Visual Studio here and haven't seen the problem. Please can you get us some more data about this problem by doing:
(i) Get rid of the add-in by...
rwwilden, thank you very much for your help getting to the bottom of this problem.
For the record, it is due to files being blocked by the operating system when they have been downloaded from an untrusted zone. They cannot be unblocked when they are placed in certain locations. The workaround is to copy them to the users local directory, unblock them there, and then copy them back.
I've logged this as RP-682. / comments
rwwilden, thank you very much for your help getting to the bottom of this problem.
For the record, it is due to files being blocked by the operating system when they have been downloaded from an un...
Hi.
Refector Pro simply generates pdb files (the debugging information) and the add-in takes care of getting those files into a place where Visual Studio will find them.
It is the CLR (and its debugging infrastructure) that takes this pdb information and tracks the mapping between this information and the generated machine code. The quality of the tracking depends on many things, including whether a debugger is attached to the process on startup, how highly the jitted code is being optimised and whether the assembly has the DebuggableAttribute.
Can you give some example scenarios we can take a look at? Do you run the code from inside Visual Studio or are you attaching after startup?
Thanks. / comments
Hi.
Refector Pro simply generates pdb files (the debugging information) and the add-in takes care of getting those files into a place where Visual Studio will find them.
It is the CLR (and its debu...