How can I make my application, so no reflector software can get it's source code
Tnx for the reply. I can't believe there is no bette way to protect your source. Misteake by microsoft...
There are many dotfuscators these days, some of them are good some of them are not that good. Here is a link for many of them.
http://sharptoolbox.com/categories/code-protectors-obfuscators
My favorites are CodeVeil, Dotfuscator and {SMARTASSEMBLY}. With these one's you can protect your source at highes level.
Hello Karioth,
No, you can't prevent invokation of methods of your types via reflection.
Thanks,
Eugene
Eugene Dolinskyy wrote:
No, you can't prevent invokation of methods of your types via reflection.
False!!. See ReflectionPermissionAttribute: http://msdn2.microsoft.com/en-us/library/System.Security.Permissions.ReflectionPermissionAttribute.aspx
As the author of the assembly, however, you generally can't control the permissions that the person who uses your assembly assigns to another assembly that may attempt to call a private method on your assembly via reflection.
Matteo Spreafico wrote:
Eugene Dolinskyy wrote:
No, you can't prevent invokation of methods of your types via reflection.
False!!. See ReflectionPermissionAttribute: http://msdn2.microsoft.com/en-us/library/System.Security.Permissions.ReflectionPermissionAttribute.aspx
Sorry, but you are not right. You can't control permissions user using your assembly will have.
If you think that you are right you can provide me with dll that can prevent me from invokation of some private method.
Eugene.
PowderGoblin wrote:
I just went through the same thing and thought it might be helpful for you and others.
I tested Dotfuscator, .NET Reactor and dotNetProtector.
So you just went through the same thing. And you registered today and wrote your first post because you thought it might be helpful...
You know, I don't mind if you try to advertise your product. But if you do it while dissimulating your intention... well, I will never try your product.