Comments
Sort by recent activity
Hi Willem,
I'm putting some improved error handling in the next build that'll mean you can send me a stack trace that hasn't been completely destroyed by our obfuscator. Then we'll be able to fix that issue with inherited properties.
I'm not sure how to reproduce the problem with inherited method taking you to the top of the source file. Could you give an example where it happens?
I understand about it opening reflector instead of decompiled code in VS in some circumstances. Unfortunately we just have to fix these case-by-case, so I'd appreciate you letting me know any examples you find.
We are thinking about making opening reflector optional, would you like it enabled by default (assuming we fix it all the time when you've already decompiled the assembly)?
Thanks, / comments
Hi Willem,
I'm putting some improved error handling in the next build that'll mean you can send me a stack trace that hasn't been completely destroyed by our obfuscator. Then we'll be able to fix t...
I've just tried it on the latest build, and I think someother fixes we've done have had the side effect of fixing this problem. Let me know if it works for you.
Thanks, / comments
I've just tried it on the latest build, and I think someother fixes we've done have had the side effect of fixing this problem. Let me know if it works for you.
Thanks,
Thanks a lot for the report, we'll make sure this gets fixed! / comments
Thanks a lot for the report, we'll make sure this gets fixed!
The garbage at the end of the stack trace is just our obfuscator, {smartassembly}.
I'm fixing a bug that gives "An item with the same key has already been added" right now, so that might make it more resilient to your initial configuration. / comments
The garbage at the end of the stack trace is just our obfuscator, {smartassembly}.
I'm fixing a bug that gives "An item with the same key has already been added" right now, so that might make it mo...
It adds the reflector symbol locations at a higher precedence than any existing symbol servers, however it shoudn't ever remove your existing symbols. That should mean that you just have to not decompile an assembly, and you'll get the symbols you already have for it.
Let me know if that isn't working as expected. / comments
It adds the reflector symbol locations at a higher precedence than any existing symbol servers, however it shoudn't ever remove your existing symbols. That should mean that you just have to not dec...
I disagree.
A lot of the time, your existing pdb doesn't come with source files, and will confuse users who think Reflector Pro isn't working.
To avoid reflector overriding your exsiting pdb files, just don't check the box when you are chosing assemblies to debug. / comments
I disagree.
A lot of the time, your existing pdb doesn't come with source files, and will confuse users who think Reflector Pro isn't working.
To avoid reflector overriding your exsiting pdb files,...
Thanks for the report. That's true, I'm working on a way to make sure that standalone reflector can always open up the location you've chosen in the object browser. / comments
Thanks for the report. That's true, I'm working on a way to make sure that standalone reflector can always open up the location you've chosen in the object browser.
Thanks,, we know about this one, hopefully will be able to fix it soon. http://www.red-gate.com/messageboard/vi ... php?t=9727 / comments
Thanks,, we know about this one, hopefully will be able to fix it soon.http://www.red-gate.com/messageboard/vi ... php?t=9727
Hi marc,
Thanks for the feedback.
We'll have a think about more indication of progress. We have to balance that kind of feedback against keeping the UI simple, but it's certainly not clear-cut in this case.
We've actually decided exactly the same about the "Show me this when I start debugging" checkbox, the next build will default unchecked. The only worry was that people would miss the reflector menu, but we haven't seen that being a problem in usability trials so far.
I hope it was just taking a long time on mscorlib, it always succeeds for us.
Yes, it does use one core per assembly.
It doesn't use symbol servers. If you've embedded any code contract into the code itself to be checked at runtime, Reflector will decompile it as if it were normal lines of code in the method. So in that sense, it should work, yes. / comments
Hi marc,
Thanks for the feedback.
We'll have a think about more indication of progress. We have to balance that kind of feedback against keeping the UI simple, but it's certainly not clear-cut in t...
Ok, 341 fixes this. / comments
Ok, 341 fixes this.