NDepend Blog

Improve your .NET code quality with NDepend

Delphi Fmx Samples ❲PREMIUM ✰❳

Happy coding, and may your FireMonkey apps run smoothly on every screen.

Start today: open Delphi, navigate to the FMXSamples folder, pick one demo that resembles your next project (e.g., CustomListView or RESTClient ), and modify it step by step. In one week of sample-driven development, you will gain the same insights that once took months of trial and error. delphi fmx samples

In this article, we will explore where to find official and community-driven Delphi FMX samples, break down essential sample categories, and show you how to adapt them to your real-world projects. Embarcadero (the company behind Delphi) provides an extensive collection of samples directly within the IDE and on their public repositories. 1.1 The Samples Directory in Your Delphi Installation After installing Delphi (from version 10 Seattle to the latest 12.x), navigate to: C:\Users\Public\Documents\Embarcadero\Studio\Samples\Object Pascal Happy coding, and may your FireMonkey apps run

Introduction: Why Samples Matter in FMX Development Delphi’s FireMonkey (FMX) framework is a powerful tool for developing native applications for Windows, macOS, iOS, Android, and even Linux from a single codebase. However, transitioning from VCL (Visual Component Library) to FMX—or starting cross-platform development from scratch—comes with a steep learning curve. This is where Delphi FMX samples become indispensable. In this article, we will explore where to

Comments:

  1. Ivar says:

    © 2026 — Savvy Orbit

    I can imagine it took quite a while to figure it out.

    I’m looking forward to play with the new .net 5/6 build of NDepend. I guess that also took quite some testing to make sure everything was right.

    I understand the reasons to pick .net reactor. The UI is indeed very understandable. There are a few things I don’t like about it but in general it’s a good choice.

    Thanks for sharing your experience.

  2. David Gerding says:

    Nice write-up and much appreciated.

  3. Very good article. I was questioning myself a lot about the use of obfuscators and have also tried out some of the mentioned, but at the company we don’t use one in the end…

    What I am asking myself is when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
    At first glance I cannot dissasemble and reconstruct any code from it.
    What do you think, do I still need an obfuscator for this szenario?

    1. > when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.

      Do you mean that you are using .NET Ahead Of Time compilation (AOT)? as explained here:
      https://blog.ndepend.com/net-native-aot-explained/

      In that case the code is much less decompilable (since there is no more IL Intermediate Language code). But a motivated hacker can still decompile it and see how the code works. However Obfuscator presented here are not concerned with this scenario.

  4. OK. After some thinking and updating my ILSpy to the latest version I found out that ILpy can diassemble and show all sources of an “publish single file” application. (DnSpy can’t by the way…)
    So there IS definitifely still the need to obfuscate….

Comments are closed.