WinForms applications are common in older .NET software, and they often store logic in form events and helper classes. Analysing one with de4dot is straightforward when you work safely and focus on the forms first. This guide explains a practical approach.
Work on a copy in a safe folder
Copy the executable and its libraries into a separate folder, and leave the original untouched. Never run an unknown program on your main system without protection. A separate folder also keeps the original, the cleaned output, and your notes easy to tell apart.
Clean the assembly and find the main forms
Run a basic de4dot pass on the copy, then open the output in a decompiler. Start with the main form and any forms that handle login, settings, or data saving. Those forms usually contain the most important event handlers and business logic.
Follow events to the logic behind them
In WinForms, a button click or menu action often calls a short event handler that then calls deeper logic. Follow each event to its handler, then to the helper methods it uses. This path is usually clearer than reading the whole program from top to bottom.
Test only in a safe environment
If you need to run the cleaned program, use a safe test environment and compare its behaviour with what you expected from the code. Record the forms you examined, the events you traced, and anything that stayed unclear, so your analysis can be checked later.
For a related workflow, see how to decompile a de4dot cleaned assembly. For safety background, see can de4dot give you a virus.
Frequently Asked Questions
Is WinForms easier to analyse than WPF
Often yes, because event handlers and forms give a clear starting point for tracing logic.
Should I clean every library
Start with the main program, then clean a library only if its behaviour matters to your analysis.
What if a form still looks unclear
Focus on its events and the methods they call, and note what remains unclear for later review.
Can I run the cleaned program safely
Only in a safe test environment, never on a system with important data, and never without checking its libraries.
What should I document
Document the main forms, the events traced, the de4dot pass used, and any unclear sections.


