Geek Answers Handbook

Can you Obfuscate build LinqToSql with a .net reactor without breaking them?

I am using .net Reactor to obfuscate a data-level assembly containing LinqToSql classes. When invoking the assembly, I get the following error.

Bad Storage property: '_ApplicationId' for member 'RCSQLData.Application_DB.ApplicationId'

I use the "Library" mode and have included "Necrobit" and "obfuscation".

Is it possible to obfuscate LinqToSQL classes or is it an old reflection nut again?

Michael

+4
source share
2 answers

Due to the fact that LINQ-toSQL uses Reflection very much. He cannot find the original properties because he is trying to find them by their original names (which are now confused).

The solution is to exclude the corresponding classes / members from renaming. Some of them, such as Crypto Obfuscator , will automatically do this automatically, detecting the use of LINQ-SQL in your code.

+3
source

Are you invoking a secure assembly in code that wants to use it? (i.e. referring to protected .dll?)

I also use .NET Reactor, but in "application mode" and .exe protection with additional assemblies, and it works fine. However, I select my main assembly and specify an additional satellite .dll that will be used, and it will be combined and protected with one shot.

I do not believe that you can add a link to the protected .dll that is in it, since it will need to think about it. I will read more about library mode and get back to you.

+1
source

More articles:


All Articles