You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Walkingtec.mvvm framework (WTM) is a rapid development framework based on .net core. It supports LayUI, React, VUE. WTM has built-in code generator to maximize development efficiency. It is a powerful tool for efficient web development.
CI Build Status
Platform
Build Server
SDK
Master Status
Develop Status
Azure Pipelines
Windows/Linux/OSX
v2.2.300
Azure Pipelines
Windows/Linux/OSX
v3.1.101
Azure Pipelines
Windows/Linux/OSX
v5.0.103
Azure Pipelines
Windows/Linux/OSX
v6.0.101
Nuget Packages
Package name
Version
Downloads
WalkingTec.Mvvm.Core
WalkingTec.Mvvm.Mvc
WalkingTec.Mvvm.Mvc.Admin
WalkingTec.Mvvm.TagHelpers.LayUI
WTM Features
WTM provides 4 types of ViewModel, covering all of the common functionalities of mainstream web applications.
CrudVM provides most common functionalities for data addition, deletion and modification.
ListVM provides paging and exporting functionality.
ImportVM & TemplateVM provides importing via excel functionality.
BatchVM provides batch operation functionality.
WTM has its own code generator, which makes development efficient and fast.
WTM provides dozens of client-side controls, including Form, Grid, Panel, Dialog and quite alot of other common controls.
WTM provides built-in user, role, user group, Data permission, page permission, menu, log, mail, SMS, file and other common back-end functionalities;
WTM supports single sign on, portal and distributed database;
WTM provides simplified integration with libraries such as Redis, DFS etc.
WTM provides both server-side and client-side frameworks for building user interfaces.
Mode
UI
Status
Server-side
LayUI
Stable
Client-side
React
Stable
Client-side
VUE
Stable
Server/Client
Blazor
Stable
Under WTM framework's client-side mode, you can also use code generator to generate server-side and client-side code at the same time, greatly reducing the communication cost of front-end and back-end developers, essentially improving the development efficiency, so that "separation" is no longer complex and expensive.