Skeleton with ASP.NetCore + Blazor (Client WASM) A few useful things about collecting to a repo (Hobby project)
A playful project with a few solutions may not be suitable for a sharp project as a lot of things were built into it that shouldn't have been, but the goal was to try them in one place.
- ASP.NET Core 3.1 WebApi
- .NET Core 3.1 / Standard 2.1 Libraries Features
- Blazor Client .Net 5.0 RC1
- SOLID principles
- ONION architecture
- DI
- Repository pattern (By Entity fw it shouldn't be because it implements the repository pattern and uow)
- Entity fw (or Dapper)
- CQRS with MediatR
- MediatR Pipeline Logging & Validation
- Multicontext DB conn.
- UOW maybe
- Healtchecks
- Automapper
- Fluent validation
- API Versioning
- REST
- GraphQl
- Swagger
- Wrappers (Pagination,...)
- Custom exception handling
- Serilog (or NLog or Elmah)
- Microsoft Identity with JWT Authentication
- Refresh Token
- Complete User Management Module (Register / Generate Token / Forgot Password / Confirmation Mail)
- Two Factor Authentication (Email, SMS, Google Authenticator)
- Background job with Hangfire
- SMTP / Mailkit / Sendgrid Email Service
- Ocelot API
- Chat with SignalR
- Push notification with SignalR
- REDIS or In-memory caching
- RabbitMq + Masstransit | Kafka
- Globalization & Localization
- Kubernetes & Docker
- LDAP & ADFS
- ElasticSearch
- MongoDB, Postgre , MySql, Mssql,DB2 ,Oracle ...
- Benchmark.NET
- OWASP
- Main dashboard screen
- Authorization
- Authentication
- Interactive Charts (Highchart,Google,D3,ChartJs,Morris,...)
- Scalable cards
- Table (filter,sort,...)
- Google map or Leaf
- Themes
- Chat
- Fonts and Styles
- PWA
- Responsive
- data from different DBs
- charts
- email sending
- chats
- machine larining examples
- fancy tables