.NET Framework and .NET Core share a common heritage, but they run in different environments and use different libraries. That difference matters when you clean an assembly with de4dot, because the runtime and dependencies can change what the tool can resolve and what the output needs to run.
The basic difference in plain terms
.NET Framework is the older Windows focused platform, while .NET Core, now known as .NET, is cross platform and more modular. A Framework program often expects Windows libraries and a system wide runtime, while a Core program may carry its own runtime or rely on a newer shared runtime. Knowing which one you have is the first step before any cleaning work.
Why dependencies matter more than the name
De4dot needs to understand the types and libraries an assembly uses. If a Framework assembly references a Windows only library, that library must be available during analysis. If a Core assembly uses a newer library version, the matching version helps the tool produce a cleaner result. In both cases, keeping the original folder structure together is a practical habit.
Checking the target before you clean
Look at the program folder, its configuration files, and any notes from the developer. Those clues often reveal the target framework without needing to open the code. If you are unsure, start with a copy, run a basic pass, and inspect the output before trying extra options. A careful first pass is better than a fast pass that creates confusion later.
What to expect from the output
A cleaned Framework assembly will usually still need its Framework environment, and a cleaned Core assembly will usually still need its Core runtime. Cleaning does not turn one platform into the other, and it does not remove the need for the right runtime. That expectation helps you test the result in the right place instead of chasing a problem that is really a platform mismatch.
For a list of protectors de4dot can handle, see the de4dot supported obfuscators list. For Windows setup checks, see de4dot system requirements for Windows.
Frequently Asked Questions
Can de4dot clean both Framework and Core assemblies
It can work with many .NET assemblies, but success depends on the protector, the libraries used, and whether dependencies are available.
Does cleaning change the target framework
No, cleaning aims to restore readable code while keeping the same target and behaviour as the original program.
Why does a cleaned Core file fail on an old machine
It may need a newer runtime, so check the target version and test the output where that runtime is installed.
Should I keep the original folder structure
Yes, keeping related libraries and configuration files together helps de4dot resolve types and helps you test the result.
How can I tell which platform an assembly uses
Check its folder, configuration files, and developer notes first, then inspect the cleaned output in a decompiler for target clues.


