# Vue.NetCore (VOL framework): a code-generator-first .NET 8 and Vue stack

> Vue.NetCore, also published as the VOL framework, pairs an ASP.NET Core backend with Vue 2 or Vue 3 frontends and generates most CRUD pages from a configuration screen. It suits teams building internal admin systems on SQL Server, MySQL, PGSql or Oracle, and it assumes you accept its generated structure rather than assembling your own.

**cq-panda/Vue.NetCore** — (已支持sqlsugar).NetCore、.Net6、Vue2、Vue3、Vite、TypeScript、Element plus+uniapp前后端分离，全自动生成代码；支持移动端(ios/android/h5/微信小程序。http://www.volcore.xyz/

- Repository: https://github.com/cq-panda/Vue.NetCore
- Stars: 4,239 · Forks: 1,370
- Language: C#
- License: MIT
- Published: 2026-09-23 · Updated: 2026-09-23 · Language: en
- Canonical page: https://hysenlabs.com/projects/cq-panda-vue-netcore

## What Vue.NetCore is, and the problem it targets

Vue.NetCore is a full-stack rapid development framework rather than a library you add to an existing application. The README describes it as a front-end/back-end separated framework whose basic functionality is entirely produced by a code generator, with roughly 300 extension methods and properties exposed across the front end and back end so that developers write business logic on top of generated code. The intended audience is clear from the feature list: teams building admin consoles, REST APIs, forms, and mobile or WeChat mini-program clients, where the repetitive work is table CRUD, master-detail editing, import and export, and permission wiring. The README also names 信创 (domestic technology stack) support, which points at organisations that must run on approved database and server combinations. If your project is a public API with a hand-designed contract, or a front end that is not an admin interface, the generator-first premise buys you little.

## Two backends, one front end: how the repository is laid out

The top-level entries make the architecture legible without opening any file. vol.api is the Entity Framework Core backend, vol.api.sqlsugar is the SqlSugar backend, and vol.web holds the front end. DB/ holds database assets, 国际化配置/ holds internationalisation configuration, and imgs/ holds the screenshots the README embeds. The README states that SqlSugar support arrived in 2023.10 and that it was not a thin addition: the back end was rewritten and the SqlSugar version is maintained independently. That matters because it means two backend codebases to track, not one with a swappable ORM. The backend dependency list is broad and conventional for this style of framework: .NET 8, EF Core 8.0, SqlSugar, JWT, Dapper, SignalR, Quartz.Net, Autofac, and SQL Server, MySQL, PGSql or Oracle, with Redis. The front end is Vue 2 or Vue 3 with Vite, TypeScript, vuex, axios and Element UI or Element Plus. SignalR and Quartz.Net are the two dependencies worth noticing: they imply real-time messaging and scheduled jobs are part of the framework's surface, not something you bolt on.

## The code generator is the product, not a convenience

The central mechanism is a generator that runs inside the framework and emits both backend and frontend code from configuration. The README states that more than 30 properties can be configured online for the generated code, and that master-detail (one-to-many) pages are generated end to end, including automatic data source binding, without writing code. Two frontend behaviours are called out specifically: tables convert keys to values automatically, and form select and checkbox controls bind their data sources without any code. That is the real claim. In a typical ASP.NET Core plus Vue project you write the entity, the service, the controller, the API client, the table columns, the form fields and the dictionary lookups by hand for every table. Here the generator produces that layer and you extend it. The README is explicit that extension is the expected path: it says the framework is less about speed alone and more about how business code is extended and how code is organised. The trade-off is that you inherit the generator's conventions. The README does not document how to regenerate a table after the schema changes, nor how to reconcile hand-written edits with a later regeneration. Anyone adopting this should treat that as an open question to answer from the source, not from the documentation.

## Installing and generating your first page

The README does not give a step-by-step install. It lists the required environment instead: Visual Studio 2022 and .NET 8 on the backend, VS Code and Node tooling on the front end, with the databases and Redis listed above. The repository ships upgrade documents at the root, including 3.ef后台升级.net8.0.docx and 4.sugar后台升级net8.0.docx, which suggests the .NET 8 migration path is documented in those files rather than in the README. The practical entry point is to pick a backend directory, restore it, and point the connection string at your database. The exact key names are not given in the README, so read the configuration file in the backend you choose before editing it.

```bash
git clone https://github.com/cq-panda/vue.netcore.git
cd vue.netcore
ls vol.api vol.api.sqlsugar vol.web
```

After cloning, the three directories above are the ones you work in. Choose vol.api for EF Core or vol.api.sqlsugar for SqlSugar, and vol.web for the front end. The README points to http://www.volcore.xyz for the Vue 3 documentation, http://v2.volcore.xyz/document/guide for the Vue 2 documentation, and http://app.volcore.xyz/ for the app, H5 and WeChat mini-program documentation. It also lists demo credentials for the hosted preview, an administrator account admin666 with password 123456, and a local super administrator account admin with password 123456. Those are preview credentials; do not carry them into a deployment. Once the backend and front end are running, the generator is used from inside the application: you configure the properties for a table, generate, and then extend the emitted backend and frontend files with your business logic.

## Where the framework will fight you

The release history is the first thing to weigh. The newest tagged release is v3.0.1 from 2021-08-16, followed by v3.0.0 from 2021-08-04 and v2.2.9 from 2021-05-23. The last push to the default branch was on 2026-05-24, so work is happening, but it is not flowing through GitHub releases. Version-to-version upgrade guidance therefore lives in the repository's own documents and archives, including 2.现有项目升级.doc and 2026.05月版本升级.zip, rather than in a changelog you can read in the browser. A team that pins dependencies and expects semantic versioning will find that awkward. The second constraint is the two-backend split. Choosing SqlSugar means tracking vol.api.sqlsugar as its own codebase; the README says it is maintained independently, so fixes and features may not land in both backends at the same time. Third, the framework is opinionated about structure. If your organisation already has a service layer, a DTO convention or a frontend component library, the generated code will either adopt those or sit beside them, and the README does not describe an adapter for either case. Finally, the documentation is split across three external sites by frontend version, so a question about the Vue 3 build and a question about the Vue 2 build are answered in different places.

## Alternatives and the difference in approach

The closest comparison in the .NET world is ABP Framework, which is also a full-stack application framework for ASP.NET Core with a module system, but its centre of gravity is dependency injection, modular packaging and a defined application layer, not a generator that writes your pages. With ABP you assemble the CRUD layer yourself or with tooling around it; with Vue.NetCore the CRUD layer arrives generated and you extend it. If your team wants explicit architecture and long-term framework governance, ABP's approach is easier to reason about. If your team's bottleneck is the volume of similar admin screens, the generator-first approach removes more typing. On the frontend side, the choice between Vue 2 and Vue 3 matters here in a way it does not in most projects: the README maintains separate documentation sites for each, and Vue 2 is past the point where new projects should start there. Vue.NetCore is also not a low-code platform in the hosted sense. The generator runs inside your own application against your own database, and the output is source code you own and must maintain, which is a meaningful difference from platforms that keep the application definition on their servers.

## Licence, maintenance and the cost of upgrading

The repository is MIT licensed, which permits commercial use, modification and redistribution provided the copyright notice and permission notice are retained. That is a permissive licence and it does not impose copyleft obligations on your application. It is not legal advice; if your organisation has a licence review process, run the LICENSE file through it, particularly if you redistribute the framework itself. The maintenance picture is mixed and worth stating plainly. The last push was on 2026-05-24, so the repository is not abandoned. The newest tagged release is v3.0.1 from 2021-08-16, so the release channel has been quiet for years. The README also advertises an enterprise edition at http://pro.volcore.xyz/, which means the open repository is not the only version of the product, and you should confirm which features exist in the MIT-licensed code before designing around them. Upgrade cost is the variable to budget for. Because the framework generates code you then edit, a framework upgrade can collide with your edits, and the repository's answer to that is a set of upgrade documents and a version archive rather than a migration tool.

## Conclusion

Adopt it if you are building an internal admin or management system on .NET 8 with Vue and want master-detail pages, forms and REST endpoints generated rather than hand-written, and if your team is comfortable reading generated C# and TypeScript instead of owning the layout. Do not adopt it if you need a documented public API contract, a stable versioned release line, or a stack you can fully audit from the repository root: the README does not document either, the newest tagged release is v3.0.1 from 2021-08-16, and the repository ships a 2026.05月版本升级.zip rather than a changelog. Before committing, clone the repository, open the solution under vol.api (EF Core) or vol.api.sqlsugar (SqlSugar), run the generator against one real table, and read the generated backend and frontend files line by line to confirm the conventions match how your team writes code.

## FAQ

### Does Vue.NetCore still exist and is it maintained?

The repository is not archived and the last push to the default branch was on 2026-05-24, so it is still being worked on. The newest tagged release is v3.0.1 from 2021-08-16, so changes are not being published through GitHub releases.

### Is Vue.NetCore a backend or a frontend framework?

It is both. The repository contains vol.api and vol.api.sqlsugar for the ASP.NET Core back end and vol.web for the Vue 2 or Vue 3 front end, and the code generator emits code for both sides.

### Which databases does Vue.NetCore support?

The README lists SqlServer, MySql, PGSql and Oracle, with Redis alongside them. It also states that SqlSugar support was added in 2023.10 by rewriting the back end into an independently maintained version.

### Is Vue.NetCore free to use commercially?

The repository is MIT licensed, which permits commercial use and modification if the copyright and permission notices are kept. The README also links to a separate enterprise edition, so check which features are present in the open repository before relying on them.

## Sources

- [cq-panda/Vue.NetCore on GitHub](https://github.com/cq-panda/Vue.NetCore)
- [Issues](https://github.com/cq-panda/Vue.NetCore/issues)
- [License: MIT](https://github.com/cq-panda/Vue.NetCore/blob/master/LICENSE)
- [README](https://github.com/cq-panda/Vue.NetCore/blob/master/README.md)
- [Releases](https://github.com/cq-panda/Vue.NetCore/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/cq-panda-vue-netcore