4.0 bugs

[Stefan Olson]

In another thread, someone asked repost any 4.0 bugs to the forum. I
sent this message earlier today to Dennis:
I downloaded the new version 4 of .net reactor. The beta didn't work
correctly obfuscating my Silverlight project, but the new version does
work correctly as long as I turn off control flow obfuscation.
Unfortunately, if I have control flow obfuscation on, at any level, I
get this exception when running my program:
System.Security.VerificationException: Operation could destabilize the
runtime.
at VirtualTourViewer.App..ctor()

Would you like me to send my project to you so you can resolve this?

In addition, i.e. get the following error when I try and merge any
assemblies in Silverlight:
System.NullReferenceException: Object reference not set to an instance
of an object.
at IY4dFoqiLe1wlnRhNEJ.rmxLtfqKiVrYtsHMWZJ.2ocRNwmjYe7QSt3M0HTr
(Object )
at IY4dFoqiLe1wlnRhNEJ.rmxLtfqKiVrYtsHMWZJ.4wTmqmoe1g(Object )

It would also be very useful if the build output all assemblies into a
single folder instead of having to go into each separate folder for
each assembly and then put each one back into the xap file. It would
be even better if we could obfuscate directly with the xap file.

…Stefan

[Denis]

Stefan,

v4.0.9.5 should solve the control flow obfuscation issue for
Silverlight assemblies:
http://www.eziriz.com/downloads/dotnet_reactor_setup_latest.exe

If you want to copy all protected Silverlight assemblies into one
folder, just change the Target File option to:
C:\mysecuredassemblies\<AssemblyFileName>

By default the Target File option is set for new v4.x .NET Reactor
projects to:
<AssemblyLocation>\<AssemblyName>_Secure\<AssemblyFileName>

In soon you will be able to select an xap file as target file as
well. .NET Reactor will add the protected files into the archive or
replace them automatically.

Greetings,
Denis

[Stefan Olson]

Dennis,

Thanks for your response. I have downloaded the update as you
suggested and receive this error message when trying to protect any
Silverlight assembly:
System.Exception: Can't access file:
D:\projectswpf\hsc\LegacyDocsSilverlight\Bin\Debug\LegacyDocs.dll
at 0P3ta09y6r58dU7YlZ8.EMN53O9cfPHJJgFbHvK.oY6dkcHE1Z(Object )

You may be interested to know that I have put a review of a number of
Silverlight obfuscators, including .net reactor on my blog:
http://www.olsonsoft.com/blogs/stefanolson/post/Selecting-an-obfuscator-for-Silverlight.aspx

...Stefan

[Denis]

Stefan,

Did you change the "Target File" option? The latest version is
successfully tested against several Silverlight assemblies. However, I
think the "Can't access file" exception isn't accurate enough. Now,
v4.0.9.6 should show you exactly what the problem is:
http://www.eziriz.com/downloads/dotnet_reactor_setup_latest.exe

You have really put much effort in your Silverlight obfuscators
review! I hope, as soon as the control flow obfuscation issue is
solved you will correct your review accordantly. :)

Greetings,
Denis

[Stefan Olson]

Yes, turns out I set target file wrong - it was trying to overwrite
itself.

However, it doesn't fix the problem that I have with control flow
obfuscation. At level 1 I get this error:
Common Language Runtime detected an invalid program

at level 9 I get this error:

Operation could destabilize the runtime.

But the actual control flow obfuscation, as far as reflector is
concerned, is excellent, because users can't examine the code in any
way.

...Stefan

[Denis]

Problem is finally solved. :) If you use the following version the
output assembly can overwrite the unprotected input assembly:
http://www.eziriz.com/downloads/dotnet_reactor_setup_latest.exe

Greetings,
Denis