Home/ Questions/Q 8400979
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T21:41:22+00:00

Have any of you had this problem before? I’m trying to obfuscate a solution

  • 0

Have any of you had this problem before?

I’m trying to obfuscate a solution written in C#/.NET 3.5 on Visual Studio 2008 SP1 on a machine running Windows 7 Professional SP1, and keep getting the same error when using Dotfuscator Community Edition

Could not find a compatible version of ildasm to run on assembly (valid path to solution output exe). This assembly was originally built with .NET Framework v2.0.50727

I’ve tried Googling and nothing much has helped so far (either that, or my Google-Fu is failing me).

I’ve tried re-installing the Windows SDK, and re-installing Visual Studio 2008, but neither have helped.

I’m assuming that it’s Dotfuscator Community edition that’s causing the problem, because a colleague is using the same xml settings file on his machine, and it obfuscates the solution no problem.

My idea is that, as it says in the error message, Dotfuscator cannot find an ildasm (the library/function used to obfuscate?) file that is compatible with .NET 3.5, only .NET 2.x. Is this a correct asusmption?

Dotfuscator had been working fine, previously. But, after a recent round of Windows updates it no longer seems to work on my machine – some of the recent Windows updates have caused havok with the network and some colleagues laptops (revoking login credentials, invalidating certain programs, the usual), that’s why I’m assuming it’s one of the updates that has caused this.

Of course, I’m not adverse to putting it down to user error, except for the fact that the same settings file and solution outputs are not causing Dotfuscator to fail on a colleague’s machine.

Any suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As you’ve guessed, this is due to Dotfuscator failing to find the proper version of ildasm for the assembly provided to it. Dotfuscator obfuscation is performed via disassembling, altering, and reassembling the assembly, so it requires versions of ilasm/ildasm that match the assembly’s target version.

    Dotfuscator will search in \Windows\Microsoft.NET\Framework{FrameworkVersionHere} for the proper version of ilasm and ildasm, IIRC. Do you have those executables in \Windows\Microsoft.NET\Framework\v2.0.50727? If not, you’ll need to get them in there – installing .NET framework 2.0 should do so (or just copy from a colleague’s computer).

    Edit to reflect comments below:
    We found that reinstalling the Windows SDK fixed the issue, likely because the Windows SDK’s registry settings had been wiped out.

    • 0