User profile for benblo

Answering my own question: to view IL, simply change the language in Reflector's options. So I guess "target offset 00CB" is the instruction number? I see stloc.1, "pops the current value from the top of the evaluation stack and stores it in the local variable list at index 1"... hmm, doesn't mean a thing to me [image] ! Maybe the disassembler could fail more gracefully, ie display the valid lines before/after the offending instruction? / comments

Answering my own question: to view IL, simply change the language in Reflector's options. So I guess "target offset 00CB" is the instruction number? I see stloc.1, "pops the current value from the ...

0 votes

I'm having the same problem with another assembly. This one was built in Mono but shows up fine, nothing is obfuscated. I can actually view the offending classes in their most part, except for a few methods that crash Reflector. FileDisassembler and FileGenerator both hang, I guess they can't do more than what Reflector gives them. I sent a bug report, the highlight being: Translation failure in 'UnityEditor.GUITemp.DoListView(Rect, ListViewState, Int32[]) : ListViewElementsEnumerator' in 'UnityEditor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'. System.InvalidOperationException InnerException: Invalid branching statement for condition expression with target offset 00CB. I don't feel comfortable sending the DLL, but if you have the courage you can download a demo of the product here: http://unity3d.com/unity/download It's a Mac app (Windows version coming soon, yay!), but I think some Windows archivers can open dmg files... :roll: Extract the app, locate the DLL, browse to UnityEditor.GUITemp.DoListView to reproduce the crash. Is there a way to read the actual CLR (if that even means anything)? I mean the app works so obviously the DLL is valid, it's just C# translation that fails... / comments

I'm having the same problem with another assembly. This one was built in Mono but shows up fine, nothing is obfuscated. I can actually view the offending classes in their most part, except for a fe...

0 votes

Thanks for the quick reply, and the "space" tip! I also check the "." option, it helps A LOT, now I don't type a whole line of code and watch back and say "jeez where's all I typed??" So I took some time to have a look at the options... I saw there's a default 500ms delay while showing the candidate list, maybe that explains in part this un-VS feeling I have. Like when I type "TableName.", on the "." I expect to see the column list instantaneously. I don't know if the delay is necessary due to some processing speed limitations, I guess I could try to set it to zero? In VS it just seems to be here when I want it, period. I know sometimes VS's intellisense is acting up and the candidate list takes a while (or forgets) to show, or I switch windows in the middle of a word, come back and the candidate list is gone: in those cases hitting alt+right brings it up for sure. Also it brings it up from nowhere, even if I'm not typing anything. I suppose all this is the equivalent of the Ctrl+spacebar I saw in the options, but can't really tell until I've used it for a while. But more important, alt+right in VS auto-completes the current word if it's the only candidate. For example now I type "ssf", wait 500ms, and hit space. In VS it'd type "ssf" then alt+right, and bam. Or I'd type "TableN" then alt+right and I'd get "TableName". I know I could just tpye "TableN" and hit space when the candidate list is up and get the same, but hey my fingers seem to be a lot faster than my brain. You said keystrokes would be "much closer to Visual Studio" and I know I can except a lot from a RedGate software (*butt-kissing noises*) so now you'll have to deliver [image] ! Anyway I hope this all helped, sorry if I'm not super clear on all this but the whole point of Intellisense is to be intuitive so I don't really know exactly how I use VS, I just know than when I launched SQL Prompt I kept typing stuff, expecting something that didn't always happen. / comments

Thanks for the quick reply, and the "space" tip! I also check the "." option, it helps A LOT, now I don't type a whole line of code and watch back and say "jeez where's all I typed??" So I took som...

0 votes

How can we help you today?

benblo

Comments