【工具】C#代码混淆工具（Dotfuscator）

dotfuscator出错解决一则

dotfuscator错误包括：

=====

Loading Assemblies...

Could not find a compatible version of ildasm to run on assembly C:\Users\Xin\AppData\Local\Temp\~XAP.0\CommonLib.dll. This assembly was originally
built with .NET Framework v2.0.50727.

Build Error.

=====

问了一下对方的support，贴上回复：

I’m not sure if you are saying you are still having the ildasm error or not. Also, are you saying that you can’t create a Dotfuscator project with the Visual Studio integrated version?

If Visual Studio integration isn’t working, you should uninstall Dotfuscator before trying a reinstall. Did you do that? You can also try a “repair” install, by opening the uninstaller in Windows Control panel and selecting “repair”. If you are doing a reinstall,
make sure the dialog which asks which versions of Visual Studio you want to install support for appears and that VS 2012 is listed. Also, you may want to delete the files at “C:\ProgramData\PreEmptive Solutions\Dotfuscator Professional Edition\4.0” before
reinstalling. This will require you to reenter the serial number for Dotfuscator if you had already entered it before. This step is not absolutely required, but if you are having problems with the installation it is worth a try.

Did you have Dotfuscator 4.9.7000 installed before you attempted to install the Windows Phone version?

If you are able to use the Visual Studio integrated version of Dotfuscator and are still getting the ILDASM error, you can direct Dotfuscator where to find the specific versions of ilasm and ildasm required by your project.

Right click on Dotfuscator project and select “properties”

Click Configuration Properties/Project Properties

Create new property (icon looks like sheet of paper)

Create the following two properties:

NAME: ILDASM_v2.0

VALUE: C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0A\Bin\ildasm.exe

NAME: ILASM_v2.0

VALUE: C:\Windows\Microsoft.NET\Framework\v2.0.50727 \ilasm.exe

Make sure that ilasm and ildasm appear on those paths. If they don’t, there may be a similar path. You would be looking for the .NET 2.0 versions of both.