**IMPORTANT**: The `conventions/` folder contains established patterns and best practices for this codebase.
Sign in to like and favorite skills
IMPORTANT: The
conventions/conventions//capture-conventionI:\surpath150\conventions\dotnet restore && dotnet buildcd src/inzibackend.Web.Mvc && yarn && gulp buildDevbuild/build-mvc.ps1inzibackend.Web.Mvcdotnet testdotnet test --filter "FullyQualifiedName=inzibackend.Tests.YourTestName"test/inzibackend.Tests/inzibackend.Tests.csprojgulpfile.jsbundles.jsonsql/surpathv2schema.sqlinzibackend.Coreinzibackend.Application.Sharedinzibackend.Applicationinzibackend.EntityFrameworkCoreast-grepast-grep --lang rust -p '<pattern>'--langrggrepinzibackend.Web.MvcThe following folders have been documented with CLAUDE.md files:
Documentation structure updated on 2025-09-27
Do what has been asked; nothing more, nothing less. NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.
In the ASP.NET Zero MVC + jQuery version (multi-page application): App services follow the classic ABP pattern and serve as the business logic / use-case layer. Key points (very concise):
App services live in the *.Application project (implementation) + *.Application.Shared (interfaces + DTOs). They are not called directly from Razor views or controllers in the traditional sense for AJAX-heavy pages. Instead: JavaScript (jQuery) calls them via AJAX → using dynamic Web API proxies automatically created by ABP/ASP.NET Zero. Typical flow: jQuery code uses abp.services.app.yourServiceName.methodName({ ... }).done(...) ABP dynamically exposes every app service method as a Web API endpoint (no manual ApiController needed in most cases). The proxy handles JSON, authorization, validation, localization, auditing, etc. transparently.
Classic MVC controllers (in *.Web.Mvc) are still used for: Initial page rendering (server-side Razor views) Non-AJAX actions Sometimes as thin wrappers that delegate to app services when returning ViewModels
Bottom line → Most interactive UI operations (CRUD, modals, datatables, etc.) → jQuery AJAX → dynamic app service API → business logic executes → JSON result back to the page. This keeps the backend clean, reusable (same services used by Angular versions too), and follows clean architecture separation.