As a work around I am building two additional assemblies that only contain these resources and that I do not obfuscate. NET Obfuscator, called the Dotfuscator Community Edition, is distributed as part of Microsoft's Visual Studio. (This is happening in two different Dotfuscator projects, in both cases VS builds fine. Here's the list of references: mscorlib, system, System.Core, System.Windows, NET assemblies (including the names of methods, properties, events, fields, types and namespaces) to a minimal set, distinguishable in most cases only by signature'. It uses massive overloading to rename metadata in. This happens even if I tell Dotfuscator to exclude everything in the resource. The project builds fine in Visual Studio and all of the references in Dotfuscator are the same as those in VS. Obfuscar is described as 'basic obfuscator for. Running C:\Program Files\\Microsoft SDKs\Windows\v6.0A\bin\ildasm.exe /OUT='C:\Documents and Settings\Owner\Local Settings\Temp\~CC.Subt.19\' /TEXT /NOBAR /RAWEH /QUOTEALLNAMES /UTF8 /FORWARD C:\KProot\ImageControls\Bin\Release\Ĭouldn't load external type because its assembly can't be found: ,System, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e It comes with a native macOS UI and it also functions more closely to the Window version of Visual Studio 2022. Dotfuscator (CE) works fine until I try it on an assembly with a resource in it then I get the following build error: Microsoft has released Visual Studio 2022 for Mac as a private preview.