Comments
Sort by recent activity
Hi.
Thank you for the feedback with regard to this bug. We haven't yet managed to reproduce it here.
On VS2008 we are simply calling into the DTE interface to determine whether the "EnableJustMyCode" property is true or false. However, if the call fails (via an exception) we then drop back into checking the registry location Software\Microsoft\VisualStudio\8.0\AD7Metrics\Engine\{00000000-0000-0000-0000-000000000000} JustMyCodeStepping which is the place where VS2005 writes changes to the setting. Hence assuming the problem is some kind of exception while the value is being checked, a workaround (if you have VS2005 on the machine), might be to configure the Visual studio 2005 on the machine to turn off "JustMyCode". That should set the value associated with the above registry key to 0. In my experiments, the value only gets written when you ok the debugging options dialog and when you have a project open. / comments
Hi.
Thank you for the feedback with regard to this bug. We haven't yet managed to reproduce it here.
On VS2008 we are simply calling into the DTE interface to determine whether the "EnableJustMyCod...
Hi.
Can you please check in the GUI that the option is turned off? It's found on the tools->options dialog in Debugging/General.
If it is off, can you tell us which version of Visual Studio you are using. In VS2008 and above we use a call into the DTE to determine the setting of the flag, and under VS2005 we look at the value of a registry setting.
Thanks. / comments
Hi.
Can you please check in the GUI that the option is turned off? It's found on the tools->options dialog in Debugging/General.
If it is off, can you tell us which version of Visual Studio you are...
Thanks for sending the example.
The functions that fail to decompile are all failing due to the same sequence of IL instructions. I have added a bug report to our bug tracking system with identifier RP-695. / comments
Thanks for sending the example.
The functions that fail to decompile are all failing due to the same sequence of IL instructions. I have added a bug report to our bug tracking system with identifie...
This is fixed in 6.5.0.56 which should be released as an EAP soon. / comments
This is fixed in 6.5.0.56 which should be released as an EAP soon.
I haven't been able to find the report. If you're happy to, can you zip up the example and send it to me: clive DOT tong AT red-gate DOT com [get rid of spaces and replace DOT and AT].
Thanks. / comments
I haven't been able to find the report. If you're happy to, can you zip up the example and send it to me: clive DOT tong AT red-gate DOT com [get rid of spaces and replace DOT and AT].
Thanks.
If you reported the error via the dialog, we should have the stacktrace already. Can you give me the name of the assembly that you were decompiling, so I can see which error report is yours?
Thanks. / comments
If you reported the error via the dialog, we should have the stacktrace already. Can you give me the name of the assembly that you were decompiling, so I can see which error report is yours?
Thanks.
Hi.
Do you have a self-contained example demonstrating the problem that you could give us? / comments
Hi.
Do you have a self-contained example demonstrating the problem that you could give us?
I've logged the failure to regenerate the switch statement as issue RP-692. / comments
I've logged the failure to regenerate the switch statement as issue RP-692.
Thanks for the feedback.
I imagine you're running a debug build and a pdb is available?
Reflector has an option, View->Options->Disassembler "Show Pdb symbols", which changes the decompilation to try to preserve symbols mentioned in the pdb.
For a small cut down example, with this option checked I get a decompilation like
string CS$4$0000 = bc.GetType().ToString();
if (CS$4$0000 != null)
{
and with it unchecked, I get
object obj2 = null;
string str = obj2.GetType().ToString();
if (str != null)
which is more like the code you'd like.
I still get a set of if statements instead of a switch and will take a look at that on Monday. / comments
Thanks for the feedback.
I imagine you're running a debug build and a pdb is available?
Reflector has an option, View->Options->Disassembler "Show Pdb symbols", which changes the decompilation to t...
Thanks for reporting this. It is currently in our bug tracking system as RP-676.
As you show in the links from your post, it would take a fair amount of work to fold the state machine that the compiler generates back into C# code. / comments
Thanks for reporting this. It is currently in our bug tracking system as RP-676.
As you show in the links from your post, it would take a fair amount of work to fold the state machine that the comp...