When I try to open some .NET Core dll the follow message appear:
Specify System.Runtime, Version=0.0.0.0, Culture=neutral, PublicKeyToken=b03f5ff7f11d50a3a
I Already try to refer manually a several System.Runtime dll, but nothing works
I use JustDecompile in another program (to automate decompiling) when we are doing analysis of C# code. Anyway, I have some DLLs in one main directory and I a restricted subset of them in another directory to test. Using the exact same arguments other than the path to access the file, it decompiles it differently. In the one with the directory with less DLLs (the testing directory), it compiles functions this way:
this.a.add_FieldChange(new FieldChangeEventHandler(this, af.a));
this.a.add_LogEntryAdded(new LogEntryEventHandler(this, af.c));
But run this against the full directory and it decompiles it this way:
this.a.FieldChange += new FieldChangeEventHandler(this.a);
this.a.LogEntryAdded += new LogEntryEventHandler(this.c);
I did not see anything in the documentation about this or about it having a switch to cause it to use one method to decompile vs another. Why is it decompiling it differently and is there a way to control one method (output) vs. the other?
I used VS2015 and it had the JustDecompile extension in there which I found very useful, upgraded to VS2017 when it came out and now I can't get the extension. An update for JustDecompile has just come out, which said that it now works with VS2017, so I've installed that - the list of VS for the extension didn't mention 2017, when will we get a VS2017 version of the extension?
I'm currently using version 2017.2.502.1 of JustDecompile