WebExpress

In the current development cycle of WebExpress 2.0.0-alpha, the framework has reached an important milestone in terms of quality assurance and stability. The current stage of development now includes more than 8,000 automated unit tests that continuously safeguard and validate a large portion of the framework's architecture. This testing foundation is complemented by extensive JavaScript and Node.js tests that cover client side components, integrations, and build processes. The large number of tests is not the primary goal itself, but rather the result of a consistently pursued commitment to quality. Every new feature, enhancement, and bug fix is accompanied by automated tests from the very beginning. This allows defects to be detected early, long before they can reach production environments. At the same time, it creates a reliable safety net for the ongoing evolution of the framework. The importance of automated testing has increased significantly throughout the development of We...

In modern software development with .NET the way we configure applications has changed fundamentally. While XML-based configuration files like a config.xml were the undisputed standard in the classic framework era the stage today belongs to cross-platform and cloud-native approaches. For a lightweight web server framework like WebExpress the switch to the modern appsettings.json offers an excellent opportunity to further increase performance while drastically simplifying handling for developers. The theoretical basis for this change is founded on the modern .NET Configuration Provider model which no longer views settings as rigid documents but as a flexible key-value store that can be dynamically fed from a wide variety of sources. The greatest advantage of this JSON-based configuration lies in its native and seamless integration into modern container environments like Docker. When WebExpress runs in a Docker container developers often need to control individual parameters such as port...

The way the framework is developed has changed fundamentally and now follows the philosophy of "from sketch to framework". While the focus was previously on manual programming, implementation is now handled entirely by Claude Code. The emphasis has shifted toward the conceptual design of ideas, where a simple mental or visual sketch serves as the direct starting point for new, production-ready components. The subsequent implementation, design, documentation, and creation of tutorial pages are fully automated from this initial concept. Compared to the traditional approach, this process is faster, more precise, more uniform, and more consistent. The human role has evolved into that of a system architect who defines requirements, provides the initial sketch, and steers the architectural direction. As a current use case, a static control ( ControlFormItemInputDnf ) for WebUI and a dynamic REST control ( ControlDataFormItemInputDnf ) for the WebApp are being implemented. This mirr...