Having written several Enterprise code generators, here are my thoughts:
- We typically have a service file for each page, and that service file implements a service interface, whereas radzen has just one service file for all entities/data.
From an organizational perspective, that would drive me crazy with so many service files in a massive Enterprise app. I would prefer there be one file for each "area" or "group." However that is defined. There is not right or wrong... It is simply a personal preference.
- We inject the service interface into components, rather than the service itself (thereby more decoupled) This is also useful when we unit test the components... we can supply mock implementations of the interfaces.
This would be nice to see in Radzen.
3 .We group pages together in a folder, Say Employees folder, Customer folder and so on, radzen puts all at root level (/Pages)
Organizationally, this would be awesome in Radzen... It is straightforward for Radzen users of all levels.
- We use code first migrations heavily
This is something I "built into" my code generators in the past. It would be very helpful if Radzen generated migrations as needed when one clicks the "Infer Schema" button.
As one who has paid for a Pro license, I'd still like to see "Out of the Box" Security implemented before anything else. 