User profile for Elmue

Hello It is really INCREDIBLE ! Right now .NET Reflector did an automatic update to version 6.6.0.30 and this old bug is NOT fixed ! 3 months have passed by and nothing happened! This explains why the quality of Relector is quite bad: Lots of bugs and even crashes are usual. The explanation is: Nobody fixes them. So what is the sense of this forum ? People can post bugs here but they are ignored. In the old times of Lutz Roeder the quality was much better. ElmÃ¼ / comments

Hello It is really INCREDIBLE ! Right now .NET Reflector did an automatic update to version 6.6.0.30 and this old bug is NOT fixed ! 3 months have passed by and nothing happened! This explains why ...

0 votes

Hello Even if the Proxy is entered correctly in the Configuration of Reflector I still can't update Reflector at work because it is not only a Username/Password problem. The Proxy requires to enter an URL like http://proxy.mycompany.com:8080/wpad.dat ________________________ But this should not be the topic of the discussion. The question is: ?? Why is it forbidden to use an old version of Reflector ?? I notice that there are several bugs in Reflector like the one that I posted here: http://www.red-gate.com/MessageBoard/vi ... hp?t=12349 But that's not all. I also have crashes in Reflector when decompiling some functions in an Assembly. Crashes are severe bugs. In older versions I did not have these bugs. So Im forced to use a new buggy version although I have an old working version that does not start anymore. That is absurd. Why dont you let the user decide which version he wants to use ? I don't need the new features in the new versions. I need a stable version that does not crash and does not change the order of the Manged C++ commands at its own will. I have the impression that you do not enough QA work before releasing a new version. With the first versions of Lutz Roeder I never had problems. My impression is that the quality of Reflector has become worse since these days. Why don't you offer beta versions that can be tested worldwide and that can be easily uninstalled by any user who has problems. In the case that I describe here: http://www.red-gate.com/MessageBoard/vi ... hp?t=12349 I would have reported the bug, uninstalled the beta version, and continued to use an older stable version that did not have this bug. With your concept of forced updates you make test phases with beta versions impossible because the user cannot go back to an older version when the beta has problems. Please allow Reflector to run always! Or do you think that it is nice to force the users to reset the system clock each time before starting Reflector ? ElmÃ¼ / comments

Hello Even if the Proxy is entered correctly in the Configuration of Reflector I still can't update Reflector at work because it is not only a Username/Password problem. The Proxy requires to enter...

0 votes

Hello This code looks correct. Although a tiny optimization would be possible: IntPtr pSrcNativeVariant = new IntPtr(); pSrcNativeVariant = new IntPtr((void*) &gvariant); could be replaced with IntPtr pSrcNativeVariant = new IntPtr((void*) &gvariant); When will the new version come ? ElmÃ¼ / comments

Hello This code looks correct. Although a tiny optimization would be possible:IntPtr pSrcNativeVariant = new IntPtr(); pSrcNativeVariant = new IntPtr((void*) &gvariant&...

0 votes

Hello I created a new demo project for you. As I nearly always get problems with email servers rejecting emails that contain an attachment with a EXE or DLL, I prefer not to send you an email. I uploaded the demo project (Source code + compiled assembly) here: http://www.electronix.ch/ptbsync/.NetRe ... ugDemo.zip ! You should fix this bug before releasing the new version 7 ! ElmÃ¼ / comments

Hello I created a new demo project for you. As I nearly always get problems with email servers rejecting emails that contain an attachment with a EXE or DLL, I prefer not to send you an email. I up...

0 votes

Hello Clive Could you reproduce the bug ? ElmÃ¼ / comments

Hello Clive Could you reproduce the bug ? ElmÃ¼

0 votes

Hello ILDASM returns the correct order. You see in the code below that VariantClear is called AFTER cNative.ConvertValue. This result does not surprise me because if the code would be as .NET Reflector shows it, it would not work. It would convert an erased variant. So the compiler is not the problem. There is definitely a severe bug ! ElmÃ¼ .method public static bool marshal( unsigned int8) ConvertValue(object o_In, [out] object& o_Out, char marshal( unsigned int16) c_Type) cil managed { .maxstack 3 .locals init ([0] native int V_0, [1] int32 b_Ret, [2] native int V_2, [3] valuetype tagVARIANT k_Out, [4] valuetype tagVARIANT k_In) IL_0000: ldloca.s V_2 IL_0002: initobj [mscorlib]System.IntPtr IL_0008: ldloca.s V_2 IL_000a: ldloca.s k_In IL_000c: call instance void [mscorlib]System.IntPtr::.ctor(void*) IL_0011: ldarg.0 IL_0012: ldloc.2 IL_0013: call void [mscorlib]System.Runtime.InteropServices. Marshal::GetNativeVariantForObject(object, native int) IL_0018: ldloca.s k_In IL_001a: ldloca.s k_Out IL_001c: ldarg.2 IL_001d: call int32 modopt([mscorlib]System.Runtime.CompilerServices.CallConvCdecl) cNative.ConvertValue(void*, void*, uint16) IL_0022: stloc.1 IL_0023: ldloca.s V_0 IL_0025: initobj [mscorlib]System.IntPtr IL_002b: ldloca.s V_0 IL_002d: ldloca.s k_Out IL_002f: call instance void [mscorlib]System.IntPtr::.ctor(void*) IL_0034: ldarg.1 IL_0035: ldloc.0 IL_0036: call object [mscorlib]System.Runtime.InteropServices.Marshal::GetObjectForNativeVariant(native int) IL_003b: stind.ref IL_003c: ldloca.s k_In IL_003e: call int32 modopt([Microsoft.VisualC]Microsoft.VisualC.IsLongModifier) modopt([mscorlib]System.Runtime.CompilerServices.CallConvStdcall) VariantClear(valuetype tagVARIANT*) IL_0043: pop IL_0044: ldloca.s k_Out IL_0046: call int32 modopt([Microsoft.VisualC]Microsoft.VisualC.IsLongModifier) modopt([mscorlib]System.Runtime.CompilerServices.CallConvStdcall) VariantClear(valuetype tagVARIANT*) IL_004b: pop IL_004c: ldloc.1 IL_004d: ldc.i4.1 IL_004e: ceq IL_0050: conv.u1 IL_0051: br.s IL_0053 IL_0053: ret } / comments

Hello ILDASM returns the correct order. You see in the code below that VariantClear is called AFTER cNative.ConvertValue. This result does not surprise me because if the code would be as .NET Refle...

0 votes

Severe Bug in .NET Reflector 6.5.0.135 : Wrong Order

Hello There is a severe bug in .NET reflector which modifies the order of the commands. The following Managed C++ code calls into a unmanaged function.bool ManagedClass::ConvertValue(Object* o_...

3 followers 9 comments 0 votes

How can we help you today?

Elmue

Activity overview