Re: Obfuscation question

Tech-Archive recommends: Fix windows errors by optimizing your registry

I am not an expert on this but I am pretty sure there is a setting on the
Dotfuscator application where you can specify not to obfuscate namespaces
and public members. You have to tell Dotfucator not to rename that otherwise
all your properties, methods etc will be renamed to something meaningless
(which is the whole purpose of obfuscating the code).



If you don't specify not to rename that then other assembly referencing the
obfuscated assembly would not work. Every time you obfuscate an assembly the
renaming can be totally different.





"Greg" <gcadmes@xxxxxxxxx> wrote in message
news:f120b1f7-c612-49fe-931d-1caf691977b6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If a company is putting together an SDK where all of their soon-to-be
shipping assemblies have been signed and obfuscated, will those
assemblies be usless without specifying the items (Namespaces,
types, ...etc) to preserve during the obfuscation process?

I've obfuscated an assembly (UserControl) using Dotfuscator CE 4.1,
created a test client app, and added the assembly reference. After
compiling the test client, it complained about not being able to find
the namespace or any class type used in the UserControl.

any suggestions?
thanks


.

Relevant Pages

  • RE: .NET and keeping my source code to myself...
    ... I understand that you need to obfuscate your assembly to ... Visual Studio .NET 2003 has provided us with a tool called Dotfuscator. ... Dotfuscator is an obfuscator for .NET assemblies. ... smaller and faster .NET applications. ...
    (microsoft.public.dotnet.general)
  • Re: How to protect intellectual property?
    ... obfuscate your code to make it harder ... you want to prevent unauthorized assemblies from calling your assembly, ... > Even more, anyone can decompile it using ildasm, change namespaces and ... > Is there a How-To on assemblies protection? ...
    (microsoft.public.dotnet.security)
  • Re: sorry i didnt saw your reply :)
    ... which uses the SQL assemblies. ... What version of Dotfuscator are you using? ... "Are you trying to obfuscate the signed assembly SqlServerCe?" ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Protecting assemblies from being used outside a company/group/team
    ... framework methods for reading the strong name from the assembly. ... > by getting the public key on the assembly and verifies that against the ... > obfuscate the code to make it much harder to reverse and inspect the code. ...
    (microsoft.public.dotnet.security)
  • Dotfuscated DLLs
    ... the same run so they use the same symbol references and are therefore ... I obfuscate these assemblies just like ... AFAIK, however, Dotfuscator doesn't support this. ...
    (microsoft.public.dotnet.distributed_apps)