Post here messages if you have any problems with working of Enigma Protector
groupThink
Posts: 15 Joined: Mon Apr 02, 2012 4:08 pm
Post
by groupThink » Mon Apr 02, 2012 4:12 pm
When protected my WPF .net application crashes on this line:
Code: Select all
XmlSerializer x = new XmlSerializer(p.GetType());
Is that because Enigma obfuscates the code and reflection doesn't work ? That said
Code: Select all
MessageBox.Show(p.GetType().ToString());
Shows the expected type name
Cheers,
Chris.
Enigma
Site Admin
Posts: 2936 Joined: Wed Aug 20, 2008 2:24 pm
Post
by Enigma » Tue Apr 03, 2012 6:55 am
Hi Chris,
This can be fixed by generating the serialisers using sgen.exe as a Post Build Event
“$(FrameworkSDKDir)\Bin\sgen” /a:"$(TargetPath)" /force
It generates a dll ({ProjectName}.XmlSerializers.dll) that makes it work. It can be included in the Virtual Box then.
groupThink
Posts: 15 Joined: Mon Apr 02, 2012 4:08 pm
Post
by groupThink » Wed Apr 04, 2012 11:49 am
That's it thanks.
Note 64 bit and .net 4.0 users will need to use the correct path:
Code: Select all
“$(FrameworkSDKDir)\Bin\NETFX 4.0 Tools\sgen” /a:"$(TargetPath)" /force
Enigma
Site Admin
Posts: 2936 Joined: Wed Aug 20, 2008 2:24 pm
Post
by Enigma » Wed Apr 04, 2012 12:01 pm
Yes, thanks you for the addition!
sanyock
Posts: 60 Joined: Sat May 12, 2012 7:36 am
Contact:
Post
by sanyock » Wed May 16, 2012 3:59 am
Is it allowed to disable obfuscation of a .NET assembly if using 3rd party obfuscator?
Btw, is obfuscation feature missing from the demo?
Enigma
Site Admin
Posts: 2936 Joined: Wed Aug 20, 2008 2:24 pm
Post
by Enigma » Wed May 16, 2012 10:34 am
Enigma Protector does not allow to obfuscate .net code, so it is even recommended to use some obfuscator before protection.
As per experience, there was not reported any incompatibility of Enigma Protector with any 3rd obfuscation tools.