How dotnetprog/dofus-alliance-manager-solution works
Project type and purpose
• This is a full-stack, .NET-centric application “dofus-alliance-manager” that combines:
• A browser-based ASP.NET Core MVC+OData WebApp with Identity and Swagger for alliance management.
• A Discord Bot service to interact with users via Discord.
• A commandline DataMigration tool for backfilling or migrating Discord messages into your system.
• A shared Core/Domain/Infrastructure library trio following a layered (hexagonal/CQRS) architecture.
• EntityFramework-backed Data and Database projects for persistence.
• A minimal AnkamaWebClient wrapper for an external Ankama REST API.
File structure
• Top-level “src/” contains multiple .NET projects:
• AnkamaWebClient (third-party API client)
• DAM.Core, DAM.Domain (application + domain logic / MediatR behaviors)
• DAM.Data.EntityFramework, DAM.Data, DAM.Database (infrastructure for persistence)
• DAM.Bot (Discord gateway service with Commands & Event Subscribers)
• DAM.WebApp (ASP.NET Core MVC + OData + Identity WebUI)
• DAM.Tool.DataMigrations (CLI for data migration)
• Common patterns:
• Core and Domain: abstraction → commands/queries under MediatR → behaviors, validators, subscribers.
• Infrastructure: EF Core services, DbContext factories, SQL scripts & migrations.
• Application: Controllers invoke MediatR requests to Core; Bot event handlers and command modules also send MediatR commands.
README for additional insights
• README only names the tool.
• But project structure clearly splits into Client → WebApp / Bot / Tool → Core → Data → Database → External services.