<div>
Do you know that obfuscation is not 100% safe? Have a look at <a href="https://blogs.msdn.microsoft.com/clrsecurity/2005/05/26/obfuscation/" rel="ugc">https://blogs.msdn.microsoft.com/clrsecurity/2005/05/26/obfuscation/</a><br />
<br />
Also, features like Reflection won't work anymore on obfuscated code.
</div>


Fractional CTO

David Favor

<div>
and specifically for your attribute, have you read <a href="https://docs.microsoft.com/en-us/dotnet/api/system.reflection.obfuscationattribute?view=netframework-4.8" rel="ugc">https://docs.microsoft.com/en-us/dotnet/api/system.reflection.obfuscationattribute?view=netframework-4.8</a>
</div>


DEVELOPPER

M THIAM

<div>
Hi guys, thanks for your answer. Your answer help me.<br />
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
</div>


<div>
Thanks to all of you to help take a good decision to propose to my boss.<br />
<br />
So i propose to keep the first approach using a wpf client and a web API in the first time<br />
And after if possible a complete migration to a web FrontEnd.<br />
<br />
Regards
</div>


<div>
You're welcome!<br />
<br />
The other big wins working with an API system include...<br />
<br />
1) Any OS can use HTTPS calls, so any client on any OS can call your API.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Caution: Once you start writing API code, you may be hooked for life. :-)
</div>


<div>
<div class="content wysiwyg-content">
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
</div>
</div>


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

How to Obfuscate a .NET Dll using Obfuscate Attribute

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.