M THIAM
asked on
How to Obfuscate a .NET Dll using Obfuscate Attribute
Hi all, i am looking for an example of use of the .NET ObfuscationAttribute to Protect a deployed DLL from reverse enginering with tool like Reflector
and specifically for your attribute, have you read https://docs.microsoft.com/en-us/dotnet/api/system.reflection.obfuscationattribute?view=netframework-4.8
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi guys, thanks for your answer. Your answer help me.
I fact i have a WPF Solution which is deployed by ClickOnce an ftp secure disk. the app is used by several stores of our company and i want to be sure if someone get the files installed he can't acces to information by decompiling the dll library
I fact i have a WPF Solution which is deployed by ClickOnce an ftp secure disk. the app is used by several stores of our company and i want to be sure if someone get the files installed he can't acces to information by decompiling the dll library
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks to all of you to help take a good decision to propose to my boss.
So i propose to keep the first approach using a wpf client and a web API in the first time
And after if possible a complete migration to a web FrontEnd.
Regards
So i propose to keep the first approach using a wpf client and a web API in the first time
And after if possible a complete migration to a web FrontEnd.
Regards
You're welcome!
The other big wins working with an API system include...
1) Any OS can use HTTPS calls, so any client on any OS can call your API.
2) API implementation is completely decoupled from API code. In other words, if you find .NET is slow or overly costly to maintain, you can just switch to running a PHP based API, which can easily sustain 100K-1M calls/minute... with no Microsoft license fees + super easy to understand for any PHP developer.
3) API speed is the big win, as you can change API caching approaches on your server side with complete abstraction of any changes to all clients/consumers, which is a massive win if your product scales quickly which require a new caching mechanism.
Caution: Once you start writing API code, you may be hooked for life. :-)
The other big wins working with an API system include...
1) Any OS can use HTTPS calls, so any client on any OS can call your API.
2) API implementation is completely decoupled from API code. In other words, if you find .NET is slow or overly costly to maintain, you can just switch to running a PHP based API, which can easily sustain 100K-1M calls/minute... with no Microsoft license fees + super easy to understand for any PHP developer.
3) API speed is the big win, as you can change API caching approaches on your server side with complete abstraction of any changes to all clients/consumers, which is a massive win if your product scales quickly which require a new caching mechanism.
Caution: Once you start writing API code, you may be hooked for life. :-)
Also, features like Reflection won't work anymore on obfuscated code.