- #DOTFUSCATOR PROFESSIONAL CRACK PRO#
- #DOTFUSCATOR PROFESSIONAL CRACK CODE#
- #DOTFUSCATOR PROFESSIONAL CRACK DOWNLOAD#
The only problem was that on error the stack trace came back obfuscated and the CE doesn't have a deobfuscator or clarifier packaged. Deploying a simple project via ClickOnce was troublesome, but achievable after manually signing the manifests with mage.
#DOTFUSCATOR PROFESSIONAL CRACK CODE#
On smaller test projects I could get the obfuscated code running with a lot of effort. I think the reason more people don't use obfuscation as a default option is that it's a serious hassle compared to the risk.
#DOTFUSCATOR PROFESSIONAL CRACK DOWNLOAD#
It's really easy to take this too far and have a negative impact on your customers and your business, do what is simple and reasonable and then don't worry about it.įor the past two days I've been experimenting with Dotfuscator Community Edition advanced (a free download after registering the basic CE that comes bundled with Visual Studio). Your biggest loss will come from casual sharing of licenses if you don't have a smart system in place, the people that break the licensing system were never going to buy in the first place. Licensing is usually the key area for most people and you should definitely be using some kind of digitally signed certificate system for licensing anyway. We used several over the years in our commercial apps and settled on Spices obfuscator from because the price is right, it does the job and they have good support though we really haven't needed the support in years anymore but to be honest I don't think it really matters which obfuscator you use, the issues and learning curve are all the same if you want to have it work properly with remoting and asp.net.Īs others have mentioned all you're really doing is the equivalent of a padlock, keeping otherwise honest people out and or making it harder to simply recompile an app. And take the time to attempt reverse engineering on what you get and see how it works with the various settings. net including asp.net and remoting, you just have to become intimate with the settings and learn how far you can push it in which areas of your code. In my experience any obfuscator will work fine with any aspect of. Actually my advice would be more along the lines of "Avoid encrypting loader type obfuscators like the plague". I've had no problems with using any obfuscator with the exception of the encrypting type which generates a loader which can be problematic in all sorts of unexpected ways and just not worth it in my opinion. We have a multi tier app with an asp.net and winform interface that also supports remoting. I would recommend key-signing your assemblies (meaning if hackers can recompile one they have to recompile all) but I don't think obfuscation's worth it. What code they got out of that would be unmaintainable and highly likely to be very buggy.
Your decompiled code ends up a long long way from compilable.Ī professional team with lots of time could still reverse engineer it back again, but then the same is true of any obfuscated code. Add lambda expressions, compiler 'magic' like Linq-syntax and var, and C#2 functions like yield (which results in new classes with unreadable names).
Try decompiling a 3.5 assembly what you get is a long long way from compiling.Īdd the optimisations from 3.5 (far better than 1.1) and the way anonymous types, delegates and so on are handled by reflection (they are a nightmare to recompile). Net 1.1 obfuscation was essential: decompiling code was easy, and you could go from assembly, to IL, to C# code and have it compiled again with very little effort.
Note: ConfuserEx is reportedly "broken" according toīack with. Sounds ominous.Ĭonfuser - an open source project which works quite well (to confuse ppl, just as the name implies). Currently in discussions to get a quotation.
#DOTFUSCATOR PROFESSIONAL CRACK PRO#
Price point is still a bit hefty.ĭotfuscator Pro - Couldn't find price on website. I was able to achieve everything I wanted and the Interface was first class. SmartAssembly - I downloaded the Eval for this and it worked flawlessly. This makes it impossible to achieve the result I needed (Merge multiple assemblies together, obfuscate some, not-Obfuscate others). Unfortunately, It is missing a key feature and that is the ability to Exclude stuff from the obfuscation.
The Licencing module was also nice and would have saved me a bunch of effort. Reactor.Net - This is a much more attractive price point and it worked fine on my Standalone Executeable. This might be a good tool but I'm not going to find out. net 3.5 and I am on Vista, support told me to give it a go but the 2005 version does not even work on Vista (crashes) so I and now I have to buy 'PostBuild2008' at a gobsmacking price point of $1900. It worked fine on XP and was a decent solution. Xenocode - I have an old licence for Xenocode2005 which I used to use for obfuscating my. I am 'Knee Deep' in this now, trying to find a good solution.
0 kommentar(er)
