Hey guys, admit, this just IS NOT FAIR

• 
  Dear maci,
  
  
  Thanks for sharing your concerns.
  
  

  maci wrote:

  But why?
  
  1) Did you silently made older versions of .Net Reflector to remove itself?

  
  We didn't: .NET Reflector has been doing this since long before we took it over, as demonstrated by this Channel 9 thread:
  
  http://channel9.msdn.com/forums/Coffeeh ... es-itself/
  
  We are considering alternatives to the current auto-update mechanism but, as I've written extensively about the update behaviour elsewhere, please allow me to refer you to:
  
  http://www.simple-talk.com/community/bl ... 90624.aspx
  

  maci wrote:

  2) Are you unable to protect Reflector with SmartAssembly, not to crash 10 times per hour? Especially when running the Reflexil plugins... Older versions don't crash...

  
  I'm sorry you've been running into problems, but without more specific information there's not much I can offer by way of help. We need to know what steps you take in order to cause these crashes to happen because we're not getting widespread reports of instability either with or without the Reflexil add-in. Note also that the crashes may be due to the Reflexil add-in itself. I'd therefore recommend you make sure you're using the latest version of both .NET Reflector and Reflexil:
  
  http://www.red-gate.com/products/reflector/index.htm
  http://sebastien.lebreton.free.fr/reflexil/
  

  maci wrote:

  3) Don't you make no further development to core Reflector, just to your VS Plugin? Reflector produces erratic code with indexers, anonymous methods, decompiled code contains variables, method and class names containing illegal characters.
  
  These are output examples from latest reflector and NOT OBFUSCATED assembly.
  
  
  >> return new GetEnumerator>d__0(0) { <>4__this = this };
  >> System.Func<MethodData,Boolean><MethodData, bool> func = null;
  >> if (CS$<>9__CachedAnonymousMethodDelegated == null)
  

  
  We have recently completed extensive work on the .NET Reflector core to provide support for the new C# and VB language constructs in .NET 4 (available in .NET Reflector 6.5, which you can download via the above link), so yes, we are continuing to develop the core of Reflector. In addition we are always striving to improve the quality of Reflector's decompilation and, as such, we have applied a number of fixes in various areas.
  
  One thing we haven't so far touched is enumerators and, in particular, the yield keyword. Reflector has never been able to decompile this correctly, in the sense that you'll always see the code generated by the compiler rather than the original syntax using yield, etc. We do plan to get around to fixing this but you're right, as yet it doesn't work (and never has).
  
  I hope you find this information useful.
  
  
  Kind regards,

  Bart Read September 07, 2010 06:36

  - 0 +
• 
  Lutz might have added the auto-delete feature, but now there's a commercial version available, it makes me very nervous.
  
  I know you've stated that you'll continue to provide the free version, but I can't help thinking of Stampy:
  
  Homer: Uh, Milhouse saw the elephant twice and rode him once, right?
  Mrs. Van Houten: Yes, but we paid you $4.
  Homer: Well, that was under our old price structure. Under our new price structure, your bill comes to a total of $700. Now, you've already paid me $4, so that's just $696 more that you owe me.
  Mr. Van Houten: Get off our property.

  RichardD September 22, 2010 14:43

  - 0 +
• 
  Curses. I was aiming for more of a Mr Burns vibe. Must try harder.

  Bart Read September 23, 2010 07:49

  - 0 +

Add comment

Please sign in to leave a comment.