Welcome to ConfuserEx discussions!

[mkaring]

👋 Welcome!

Let's use Discussions as a place ask questions, collaborate on new ideas, and connect with members of our community. Feel free to:

• Ask any questions you’re wondering about
• Share ideas
• Engage with other community members

Please be sure to welcome others and are open-minded.

[NaveenBadal]

Hello,

I built a custom application , in which I integrated the ConfuserEx.CLI application. I am running the ConfuserEx.CLI on background and showing the output in my custom textbox that I am receiving from command line.

My first question is that:
Is there any way to get the progress bar value from command line, as when the enabling newtonsoft.json compatibility step is running, it is almost taking half an hour and may be more. So I want to show a progress in that.

Second question is that:
Why is NewtonSoft.Json Enabling Compatibility step talking too much time? Is there any way to reduce its time?

[mkaring]

Hi,

Currently there is no way to get any report of the progress from the ConfuserEx CLI.

The Newtonsoft.Json compatiblity message isn't taking any time. It's just the last log message, before ConfuserEx is starting to analyze the structure and cross references of the entire assembly. Depending on the size and complexity of the assemblies you are working with, this may take some time. Mind you: Half an hour seems very excessive. What size of project are we talking about here?

[NaveenBadal]

Hello,

The count of DLLs that I am obfuscating is around 35. But not all of the DLLs uses the NewtonSoft.json. Only some of them uses it. I tried with both Confuser Ex GUI tool and with ConfuserEx.CLI, in both the tool, all other processes are not taking time, but this Found Newtonsoft.json, enabling compatibilty alone taking lot of time. On an average it is taking around 30 minutes. Maximum it takes 45 minutes to perform this step. Yes the project is big, but I don't think so, It should take that much time. Because all others steps, together will complete may be in 5 to 10 minutes.

[mkaring]

The Newtonsoft.JSON compatibility is enabled, if it's detected in any assembly. How ever as I said: Once that message appears the compatibility is already enabled and the work this step does is done.

It's impossible to tell what is taking so long in the analysis step for the rename protection that causes you so see such an extensive delay, without the assemblies that are causing this issue.

[ashahabov]

What value of "rule.preset" attribute does mean?

I am not sure that completely understood how minimum, normal, etc. values of rule.preset affect on obfuscation. Each value contains predefined set of protections — "anti debug", "anti dump", "anti ildasm" etc?

[mkaring]

The presets are, as you already suspected, a predefined set of protections that are applied if you select that option.
You'll find in the wiki what protection is enabled at what preset. Protections that are part of a lower preset, are also enabled on a higher preset.

For example: The anti debug protection is part of the "Minimal" preset. Meaning if you choose, "Minimal", "Normal", "Aggressive" or "Maximum" it will be enabled.
The anti tamper protection is part of the "Maximum" preset and will only be enabled when choosing "Maximum" as a preset.