Enterprise Web
The Enterprise Web target, the full-stack target, produces a full-stack web application: a .NET server and an Angular client, with a database.
What it produces
For the full-stack target (.NET and Angular), each kind of model produces a recognisable part of the solution.
| Kind of model |
Produces |
| Business objects |
Domain classes, business logic and data access, plus the matching Angular domain types |
| Forms |
Controllers, view models, the Angular page for each screen, and resource files |
| Services |
Exposed service projects and their controllers, including MCP tools |
| API adapters |
Client code for the systems you call and the structures they exchange |
| Automation flows |
Workflow code, with schedules registered at start-up |
| Reports |
Report classes that render the designed document |
| Data mappings |
Transformation code between the left and right structures |
| Configuration |
Roles and permissions seeded into the database, plus settings |
Logic written in the language is translated to C# for the server.
Stack at a glance
The tiers, layers and frameworks this target builds on, with their versions. The .NET version is chosen per application.
|
|
| Application Type |
Web Application |
| Language |
C# |
| Framework |
ASP.NET Core 5.0 - 10.0 / Angular 17 / 21 |
| Tiers |
Layers |
Frameworks |
Components |
Patterns |
Tools |
| 3 |
7 |
17 |
24 |
14 |
19 |
1 Client Tier
Angular single page application, built with the Angular CLI and served as static files by the backend.
| Area |
Technology |
| Client |
HTML 5, CSS (LESS / SCSS) 3, Typescript 5.2.2 (Angular 17) / 5.9 (Angular 21) |
| Real Time Communication |
WebSockets |
User Interface Layer
| Framework |
Version |
Notes |
| Angular |
17.1 (default) / 21.2 |
Single Page Application, Component-based UI |
| PrimeNG |
17.18 / 21.1 |
|
| PrimeFlex |
3.3 |
|
| RxJS |
7.8 |
|
| ngx-translate |
15 / 17 |
|
| Chart.js |
4.4.4 |
|
| FullCalendar |
6.1 |
|
| Component |
What it is |
| Form Components |
One Angular component (template, class and module / standalone config) per form, master page and partial view |
| Control Library |
Reusable framework components (grids, lists, charts, calendars, maps, modals, file attachments etc.) shipped with every application |
| Domain Model & View Models |
Typescript representation of the domain classes and of the data each form manipulates |
| Client Side Logic |
Form actions, rules and calculated expressions transpiled to Typescript |
| Themes |
Application themes generated as LESS stylesheets |
| Localization Resources |
Translation files per supported language |
Communication Layer
| Framework |
Version |
Notes |
| Angular HttpClient |
|
REST |
| SignalR client (@microsoft/signalr) |
8.0 |
|
2 Application Tier
The application tier assumes both the web server and the application server are hosted together on a single computer, virtual machine or container. They can optionally be generated as separate, decoupled applications.
| Area |
Technology |
| Web Server |
Kestrel, Internet Information Services (IIS), NGINX |
| Application Server |
.NET Runtime (Windows / Linux) 5.0 - 10.0, Docker |
| Middleware |
ASP.NET Core Middleware Pipeline, Autofac 6.1 - 9.3, Swagger (Swashbuckle) 5.6 - 10.2, Health Checks, log4net 2.0 - 3.3, Redis (optional distributed cache) |
Data Access Layer
| Framework |
Version |
Notes |
| nHibernate |
5.3 - 5.7 |
Repository, Domain Model, Session Per Request |
| Fluent nHibernate |
2.1 - 3.4 |
|
| Component |
What it is |
| POCO Classes |
Representation of Domain Model Classes in C# |
| nHibernate Repository |
A repository class that retrieves and persists entities to the Database |
| nHibernate Mappings |
Fluent mapping classes that describe the way entities and associations are mapped to the Database |
| Second Level Cache |
nHibernate caching backed by in-memory or Redis distributed cache |
Security Layer
| Framework |
Version |
Notes |
| ASP.NET Core Identity |
5.0 - 10.0 |
Cookie (Forms) Authentication, Windows Authentication, Identity Server (OpenID Connect), External Login (Google, Facebook), JWT Bearer Tokens, Claim-based identity |
| Component |
What it is |
| Identity Manager |
Extends ASP.NET Core Identity using the zAppDev Framework security module |
| Authorization Manager |
Authenticates requests and supervises access to Controller Actions and exposed APIs, based on roles and permissions |
| Security Helper |
Quick access to common operations and properties like sign in, sign out, currentUsername etc. |
Logic Layer
| Framework |
Version |
Notes |
| zAppDev .NET Framework |
12.4 - 12.6 |
|
| ASP.NET Core SignalR |
|
|
| AutoMapper |
10.1 - 14.0 |
|
| Component |
What it is |
| Business Logic |
Domain class functions in form of C# extension methods |
| Events |
Real time application events implemented in a Signal R Hub API |
| Exposed APIs |
Custom APIs exposed as REST, SOAP or MCP (Model Context Protocol) services, documented with Swagger |
| External APIs |
Consumers of external REST, SOAP, GraphQL, messaging (RabbitMQ) and DLL based services |
| Workflows |
For orchestrating domain specific functional processes, including scheduled (cron) execution |
| Data Transformations |
For quick data mapping between different structs |
| Reports |
Report definitions rendered by the built-in reporting engine |
Presentation Layer
| Framework |
Version |
Notes |
| ASP.NET Core MVC |
5.0 - 10.0 |
Model - View - Controller, REST |
| Newtonsoft Json |
12.0 - 13.0 |
|
| Component |
What it is |
| Controllers |
Basic form logic in C# classes, called by the Angular client |
| View Models |
Representation of the data a form manipulates, exchanged with the client as DTOs |
| Web API |
Entry points for the exposed APIs |
| SPA Host |
Serves the compiled Angular client (ClientApp/dist) as static files |
3 Data Tier
| Area |
Technology |
| Database Server |
Microsoft SQL Server 2012 - 2022, MariaDB, MySql, IBM DB2 / Netezza (optional) |
Settings
The settings of the target are in the Configuration editor, under Implementation Strategy. See Implementation Strategy for the overview and the settings, and Deploying Applications for the settings a deployment needs.
Database
Business objects are mapped to a relational database. How inheritance is mapped is a setting of the target: see Implementation Strategy. The deployment guide uses SQL Server.
Run it
The generated application is a standard .NET and Angular solution. You can browse its code in Studio, download the solution, or deploy it. See Download and export and Deploying Applications.