If you've been in the .Net Dev space for any time, you've probably heard of Dotfuscator. But what you might not know are the people behind it. I've been dealing with a number of them, from Sales to Support, and every single time I come away happy. They are not a company that takes their money and runs, instead continue to look for ways to help use it, use it better and improve their communication (and of course, their products!). Even when you submit what you think is a bug, and instead, it's that you are doing it wrong (not that that ever happened to me ;), they are professional and above all, friendly.

Dotfuscator is an amazing 'multi-purpose' piece of genius (e.g., includes software protection and hardening services for developers, architects, and testers), so it's hard to choose what I like best. However, our team's most pressing need was directly related to securing devices to detect if our application is running on a rooted Android device. If so, terminate and/or respond to sessions on these devices.

I really like to use this tool, it's easy to use, with many options to protect the source code, and a very good speed of processing. I used it for about 5 years withouth any problem on deployment environments. This tool really helped us to avoid the intellectual property stealing from some customers who rented the solution developed but required to install it on their own servers due security concerns. Tech support is always kind and helpful, when needed.

Dotfuscator does what it says: It protects your .NET applications. There are many features. We just use the basic code obfuscation and this works great. Their support is very helpful if you encounter any issues or need help. As it is more or less an industry standard product, you can find plenty of tutorials and help online. Also the documentation is very good. Honestly, once put in place and set up, you could almost forget about it. Which is a good thing.

My initial implementation of Dotfuscator was an attempt at obfuscation without any changes to the source code. I used the Dotfuscator config editor to create the config files using the default obfuscation configuration and added those to my source. Then by utilizing the private NuGet package on Microsoft's hosted build agents for Azure DevOps, I used the Dotfuscator CLI pipeline task to perform obfuscation on-demand during deployment. It took me only a matter of hours to put things together, and after obfuscating my assemblies using Dotfuscator, 100% of my integration tests passed on the first run. Due to this success, we are pursuing the obfuscation of our mobile code using Xamarin.

Love the string encryption and removal features. It is great to know that my apps are protected

Good language to learn for beginners very helpful and easy to understand