Activity overview
Latest activity by binkle
SmartAssembly.InformationException: SmartAssembly has encoun
Hi,
I'm getting:
SmartAssembly has encountered an error while running your project.
Failed: SmartAssembly.InformationException: SmartAssembly has encountered an invalid symbol:
The symbol SmartAs...
+1 for me to please.
We like to use it for solutions containing several projects with several entry points (4-7 exe files) and more than 10 shared dlls.
Until now we used DeepSeaObfuscator, but it's no longer developed and does not work for assemblies compiled with VS2015.
DeepSeaObfuscator allowed to pass a bunch of assemblies (simply passing an VS solution file would even be better), like you do when merging or embedding, but without the need to merge or embed.
It then analyses all assemblies and applies the best obfuscation regarding all of them.
E.g.: if there is a public method in one of the shared dll assemblies but not used in all of them it was able to strip (or at least also obfuscate) that method although it's public.
The same goes to classes and other elements.
When I now like to use SmartAssembly but you tell that it's not able to deal with such (bigger) solution?
And I need to create one project-settings file for each assembly?
When do you plan to support this?
This may be a good reason for us not use SmartAssembly because single assembly protection can never be as good as a protection regarding all assemblies of a solution.
Greetings
Harald / comments
+1 for me to please.
We like to use it for solutions containing several projects with several entry points (4-7 exe files) and more than 10 shared dlls.
Until now we used DeepSeaObfuscator, but it'...