dotfuscator

问题 I began to use Dotfuscator Community (fresh download) with Visual Studio 2019 integration as part of my Xamarin.Forms build process. I did the steps listed under: preemptive When I build, I get the correct build messages from Dotfuscator. My problem is, that while Dotfuscator obfuscates the resulting assembly of the shared project, which I can verify by opening the .dll file with ILSpy in the Release's folder, the "same" dll inside the resulting APK is not obfuscated which I can verify by

问题 I began to use Dotfuscator Community (fresh download) with Visual Studio 2019 integration as part of my Xamarin.Forms build process. I did the steps listed under: preemptive When I build, I get the correct build messages from Dotfuscator. My problem is, that while Dotfuscator obfuscates the resulting assembly of the shared project, which I can verify by opening the .dll file with ILSpy in the Release's folder, the "same" dll inside the resulting APK is not obfuscated which I can verify by

问题 What is Map.Xml and Dotfuscator1.Xml files of PreEmptive Protection Dotfuscator exe file. Should I keep them for some reason or maybe it is needed for project exe file assembly? 回答1: The Dotfuscator1.xml file is the Dotfuscator project (i.e., configuration) file. It is an XML file that defines what assemblies will be processed by Dotfuscator, where the protected assemblies will be written, and any custom configuration of the protection process (e.g., any names that will be excluded from

问题 We have an app with a manual packaging process (MakeAppx.exe). We would like to publish this app to the Store including the public symbols files, so that I can download the .cab process dump file for crash analysis (such as described here). I understand the .appxupload is a zip-file contaning the .appx package and an .appxsym file, which in turn is a .zip file containing the .pdb files (also according to MSDN). Is it safe to manually generate/edit these .appxsym and .appxupload for publishing

问题 If one will release a ClickOnce version, how can it be obfuscated by Dotfuscator? 回答1: You can use the commercial version of Dotfuscator to automatically obfuscate a ClickOnce application by adding the deployment manifest ("foo.application") as an input to your Dotfuscator project. Dotfuscator will allow you to add any necessary exclusions to the assemblies contained in the ClickOnce application and will create updated deployment and application manifests containing the obfuscated assemblies.

问题 How does Dotfuscator work? I tried obfuscate some of my classes and it renamed the methods/class to a, b, c etc. But I can still see the code inside those methods? Is it that, I am doing something wrong? Is there anything that would prevent a totally block deassembling my assembly? 回答1: That is the way it is supposed to work. Your code is still accessible, just more difficult to understand. If you want something "stronger", take a look at Xenocode PostBuild. 回答2: Code obfuscation goes well

问题 Some info: -Small application using a SQLite encrypted database -Using Dotfuscator Community Edition I still can take a look inside of the code (even with methods's names obfuscated) sQliteConnection.SetPassword("Password=ThisIsMySuperSecretPassword"); -I don´t need a high level of protection about the code itself (the logic), but I need to protect the database password If I use some concatenation like PartA = "ThisIs" PartB= "MySuper" PartC= "SecretPassword" Password = PartA + PartB + PartC

问题 I prepare my application to release ( android ) , during perform integration dotfuscator , described in https://www.preemptive.com/dotfuscator/pro/userguide/en/getting_started_xamarin.html On build of android project receive following error PreEmptive.Dotfuscator.Xamarin.targets(251,9): error MSB4184: The expression """.TargetName" cannot be evaluated. Method 'System.String.TargetName' not found. I get the file PreEmptive.Dotfuscator.Xamarin.targets as is. Should it be changed after download

问题 I have some client side HTTP RESTfull code which depends on the comfort that .net compiler generated anonymous types provide. anonymous type example0 : string prop_1 = "strValue1"; int prop_2 = 5; new { prop1 = prop_1, prop2 = prop_2}; anonymous type example1 : new { prop1 = "strValue1", prop2 = 5}; anonymous type example2 (also valid): string prop1 = "strValue1"; int prop2 = 5; new { prop1, prop2}; The problem here is, that the names of the compiler generated anonymous type's properties are

问题 This is a Dotfuscator noob question -- I'm trying to run it on some assemblies for the first time, but I get an error saying: "Invalid assembly [foo.dll]. Input assembly [foo.dll] was compiled with a version of the .NET Framework (v4.0.30319) that is not supported by this version of Dotfuscator. Please check for an updated version of Dotfuscator." I'm using the version that shipped with the current version of VS 2010, and I have all service packs etc installed. I have registered the product.