xsharp.eu • X# and .Net Reactor
Page 1 of 1

X# and .Net Reactor

Posted: Fri Feb 10, 2017 8:43 pm
by George
Hi DevTeam,

I tried to protect one Vulcan app compiled with X#.
I am using .NET Reactor. When I try to specify the Main assembly (EXE), the attached error appears.

regards
George
dotNetReactor.PNG
dotNetReactor.PNG (69.7 KiB) Viewed 245 times

X# and .Net Reactor

Posted: Fri Feb 10, 2017 9:49 pm
by Chris
Hi George,

A google search shows a lot of hits for that, also with c# apps. For example:

http://stackoverflow.com/questions/3504 ... et-reactor

Are you using the latest Reactor version? Some posts suggest that a newer version fixes this problem. Also please try deleting the .pdb files of your app before using Reactor, as suggested in the above link, does it work this way?

Chris

X# and .Net Reactor

Posted: Fri Feb 10, 2017 10:38 pm
by George
Hi Chris,

yes, I deleted the .pdb file and the Reactor opened the project correctly.
But, why that no happens with the Vulcan generated EXE ?

regards
George

X# and .Net Reactor

Posted: Sat Feb 11, 2017 12:41 am
by Chris
Hi George,

That's because vulcan is an outdated compiler :-)

The x# compiler shares the same backend with a very recent version of the c# compiler (Roslyn), which emits much more sophisticated code/pdb information than vulcan does. It looks like Reactor cannot (yet?) properly "understand" some of this symbol information.

Chris

X# and .Net Reactor

Posted: Sat Feb 11, 2017 8:34 am
by George
Chris,

>That's because vulcan is an outdated compiler :-)

You are right.
The .Net Reactor's version is the old 4.0.
I will upgrade it to 4.9 or (I see it now) in 5.0.

thank you
George