anjoy8/blog.core

💖 ASP.NET Core 8.0 全家桶教程,前后端分离后端接口,vue教程姊妹篇,官方文档:

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 12th, 2026
Created on August 17th, 2018
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 1,429
Total Stargazers: 5,283 (+0)
Total Subscribers: 158 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.1 days
Mean response time: 17.5 days
90th percentile: 20.8 days
Tracked items: 10

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 599 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • 已修复 (3)
  • 已完成 (3)
  • 欢迎提交PR,给社区一起做贡献~~ (2)
  • 跟进中 (2)
  • BUG (1)
  • 很棒的提议 (1)
  • 需要高手帮忙 (1)

Most active issues this week

Detailed Description

Blog.Core is an enterprise-grade backend API framework built on ASP.NET Core that provides a ready-to-use foundation for full-stack applications with role-based access control.

The project addresses the need for a complete, production-ready backend architecture by combining ASP.NET Core with a separation-of-concerns design pattern. It implements dependency injection through Autofac, data mapping via AutoMapper, and database access using SQLSugar. The framework includes JWT authentication, CORS support, and a role-based access control system with administrative features. It exposes functionality through a Swagger-documented WebAPI and integrates Redis for distributed caching and session management.

Teams building enterprise applications with .NET Core should consider this framework if they need a pre-configured backend that handles common architectural concerns out of the box. The project pairs with a Vue 2.x frontend counterpart, making it suitable for organizations pursuing a frontend-backend separation strategy. It includes administrative capabilities such as department-based data permissions, online user tracking with forced logout functionality, and user blacklist management. The framework targets developers who want to avoid building these foundational layers from scratch and prefer working within an established architectural pattern rather than assembling components individually.

Development activity shows consistent engagement with the codebase through multiple contributors working on core framework modules and component enhancements. The project maintains active communication with its user base through issue tracking and provides documentation via an official website. The maintainers actively solicit feedback from production users and offer customized guidance for organizations using the framework in commercial settings.