Whenever I browse for a dll and click on it, JustDecompile generates code lines with v1, v2, v3.. instead of variables and lable1, lable2... instead of lables

... W2BPM V_0 = this.mobjSession.W2BPMObject;
W2ExecutionContext V_1 = this.mobjSession.W2ExecutionContext;
BPMResult V_2 = null;
string V_3 = string.Empty; QueueElement
V_4 = V_0.RetrieveStepQueueElement(V_1, this.mobjStepData.StepIdentifier);
bool V_10 = V_4 != null;
...

 

if (!V_10) 
    { 
    V_10 = this.SaveSubTasks();
     if (V_10) 
        { goto Label2; } 
    return; }
Label2:
if (this.mstrReassignTo == string.Empty)
{ name = true; }
...

 

 

 

 

Is there any way to fix it? 
thanks,
Shuli.

 

Hello, Shuli,

 Thank you for getting in touch with us.
The problem with variable names comes from the fact that the compilation process doesn't preserve the names of the local variables, thus, JustDecompile must produce some legal names for them. It usually gives much prettier names than the ones you've observed. Are you sure you're not using an older (probably still beta) version of JD?
If you observe this problem with our latest version (2012.2.815.6) we'll really appreciate if you can send us a sample DLL, so we can investigate it further.

Greetings,
Yordan Dikov
the Telerik team

It'd be nice to have some control over the names generated by JustDecompile. The names that JD puts out are often hard to do a simple search-and-replace on, like "str", "str1", "str2", etc - if I know that "str" should be "sillyString", I can't just do a simple search and replace for "str", because it'll match too many other possibilities.
It's also a little hard to tell if a variable name is one you've created yourself (I occasionally use "str", "str2", etc), so it'd be nice to at least have the option of specifying a prefix or naming scheme for variables created to match unnamed variables in the IL.

That is a viable suggestion. It'd be really nice if you could post it to justdecompile.uservoice.com so that other users could vote on it? We use our uservoice site to prioritize future features.

Kind regards,
Tsviatko Yovtchev
the Telerik team