Need to decompile different versions of the same dll

• 
  Thanks for the suggestion. The system should save the decompiled pdbs and source when you have to switch, so the process should be very quick, but I understand it'd be nice to avoid using the dialog at all.
  
  I've put it in the bug tracker, but I can't promise that we'll have time to do it this version.
  
  Thanks,

  Alex D November 10, 2009 05:35

  - 0 +
• 
  this has gotten worse, if anything. i'd been in VS2010 and debugging something in System.Windows.Forms. I then switched to VS2008 and was debugging something slightly different in SWF. It kept telling me something like "A different version of SWF was found than what Reflector was expecting - found version 2, expected version 4" - even after telling it to decompile version 2.0. had to clear the cache completely to get it to work, which meant losing the decompilations of everything else i was working on.
  
  Maybe something as simple as having a different cache folder for different versions of the IDE would work?

  blindahl January 05, 2010 19:39

  - 0 +
• 
  That doesn't sound like the intended behaviour. We'll take a look.
  
  Cheers,

  Alex D January 06, 2010 12:29

  - 0 +
• 
  I've just fixed, in internal build 799, the problem where you're debugging System.Windows.Forms v2 in 2008 and System.Windows.Forms v4 in 2010. In the previous version you'd get the warning "A different version of SWF was found than what Reflector was expecting - found version 2, expected version 4" (in the 2008 Visual Studio) and in this latest version you won't get the message.
  
  However, in the old builds, despite the error message you ought to have been able to continue stepping into both versions. Do you have steps to reproduce a case where you need to clear the cache to get things working?
  
  Thanks

  Clive Tong January 12, 2010 10:20

  - 0 +
• 
  no, i don't, unfortunately. i'll give it a try in the next day or two if i can. i think i was depending on the veracity of the message, and just tried to do what i had to in order to make it go away. it's still happening (just saw it a minute ago, in fact), so i'll try when i can.

  blindahl January 12, 2010 16:14

  - 0 +
• 
  Haven't seen any 'false alarms' since the fix, thanx!
  
  One suggestion - in the dialog that comes up when there _is_ a mismatch, could we get a "decompile the right one" button? would save having to remember which one it was when i finally get around to selecting assemblies.

  blindahl January 21, 2010 10:44

  - 0 +

Add comment

Please sign in to leave a comment.