The problem is the assembly resolving.
The releases/2.0 is the furthest when it comes to preparing for the new versions of .NET, because that one has at least a proper handling for the runtime assemblies that would allow supporting the runtime up to .NET 5.
That does not change that resolving the assembly references currently always snaps back to the .NET Framework that that is something that needs to be adressed.

Everything up to .NET Core 2.x and .NET Standard 2.0 can work when explicitly referencing all the required assemblies in the project file.
.NET Core 3.x, .NET Standard 2.1 and .NET 5.0 I was not able to get working to this day without changes to the current version of ConfuserEx.

@NotoriousRebel: I am unsure if I understand correctly what you are trying to say here. But if you want to use the Confuser.Core.dll in your project, that is an entirely different topic.

The runtimes ConfuserEx is able to obfuscate and the version of .NET ConfuserEx itself uses to run, are two different things.

Now regarding the plan moving forward:

The proper support for .NET Standard, .NET Core and .NET >= 5, will be part of the 2.0 release. I'm planning to work on that once the 1.5 release that is close to completion now is released.
ConfuserEx 1.x itself will remain a .NET Framework 4.6.x application. Due to the way the runtime code deployment works, it has to remain a .NET Framework application.
ConfuserEx 2.x is already mostly migrated to .NET Standard. The command line application works as .NET Core application and only the user interface is currently a .NET Framework 4.6.1 application. The plan is to migrate everything that can't be .NET Standard to .NET 5. The .NET Framework version will be dropped. This does not mean that the support for obfuscating .NET Framework applications will be dropped.

Uh oh!

.NET Core, .NET Standard, .NET 5 Support #302

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions