How dtcanal/uclmultileagueapp works
1. This is a .NET desktop application, most likely WPF, organized in a layered architecture with clear separation between UI, application orchestration, domain contracts/models, and infrastructure implementations.
2. The UI layer lives under UI/ and contains the WPF view (UI/View/UCLMultilig.xaml), its UCLMultiligViewModel, custom commands, behaviors, converters, validation rules, and a WindowFactory. This layer is responsible for presentation state, binding, and user interaction only.
3. The application layer under Application/ coordinates long-running business workflows. It is split into jobs and services, with separate paths for UCL ranking and UCL schedule handling. These services likely orchestrate fetching data, maintaining state, and pushing updates to the UI or external systems.
4. Job execution is handled through Quartz: Application/JobListener/QuartzJobListener.cs and the job classes under Application/Jobs/. The job layer suggests scheduled or recurring background processing rather than purely user-triggered actions.
5. The core layer under Core/ defines the app’s contracts and models. Interfaces like IRankingServiceUCL, IScheduleService, IPing, ILoggerService, and observer interfaces define the boundaries between business logic and implementations. Models such as Match, Team, UCLRankingModel, and UCLScheduleModel represent the shared data shape across layers.
6. The infrastructure layer under Infrastructure/ provides concrete implementations for those core interfaces. It includes services for UCL ranking, UCL schedules, commentators, pinging, logging, and job rescheduling. This is where integration details are concentrated.
7. External-facing integration appears to include at least a Vizrt client (Infrastructure/VizrtClient/) and a “main server” ping/reporting flow (IPingMainServer, PingService). That suggests the app consumes or synchronizes sports data and then publishes commands or state to downstream broadcast/graphics systems.
8. Configuration is centralized in Infrastructure/Configurations/ and Infrastructure/Settings/. The presence of settings for data paths, job intervals, UCL ranking, UCL schedule, and Vizrt servers indicates the runtime behavior is strongly environment-driven.
9. State management is split by domain. For ranking there is RankingStateService, observer services, and both live and manual ranking services. For schedules there are schedule match app/observer services. This implies a publish/subscribe or observer-style update flow from fetched data to UI/state consumers.
10. Logging and error handling are also infrastructure concerns. ILoggerService plus DeafultLoggerService/LoggerService handle diagnostics, while Infrastructure/Exceptions and the Result helper indicate explicit result/error propagation across service boundaries.
11. The app uses typical WPF support pieces: converters for display formatting, validation rules, behaviors, and a relay command implementation. Those are supporting UI mechanisms, not business logic, but they shape how view state is transformed and interacted with.
12. Build and deployment are desktop-oriented. The repo includes a .sln, .csproj, GitHub Actions workflow for desktop builds, and an Inno Setup installer script (InnoInstaller.iss), which indicates the output is packaged as an installable Windows application rather than deployed as a web service.
13. For an architecture diagram, the main flow is: WPF view → view model → application services/jobs → core interfaces/models → infrastructure implementations → external systems such as live ranking sources, schedules, logger/ping endpoints, and Vizrt. The key boundaries are UI vs orchestration vs contract vs implementation.
Main entry points: UCLRankingLiveAppService.cs Ranking AppSvc · UCLMultiligViewModel.cs Main VM · UCLScheduleMatchesAppService.cs Schedule AppSvc · Match.cs Domain Models
Components 22
UI
WPF presentation, binding, and interaction layer
- App Shell · Application startup and WPF host wiring
App.xaml - Main View · Primary desktop UI for multileague workflows
UI/View/UCLMultilig.xaml - Main VM · Presentation state and command coordination
UI/ViewModels/UCLMultiligViewModel.cs - UI Support · Commands, converters, behaviors, validation, and window factory
UI/Commands/RelayCommand.cs
Application
Workflow orchestration and scheduled jobs
- Job Listener · Receives Quartz job lifecycle events
Application/JobListener/QuartzJobListener.cs - Ranking Job · Recurring UCL ranking execution
Application/Jobs/UCLRankingLive/RankingLIve.cs - Schedule Job · Recurring UCL schedule execution
Application/Jobs/UCLSchedules/UCLScheduleMatches.cs - Ranking AppSvc · Coordinates ranking workflow and state updates
Application/Services/UCLRankingService/UCLRankingLiveAppService.cs - Ranking State · Holds and publishes ranking state
Application/Services/UCLRankingService/RankingStateService.cs - Ranking Observer · Bridges ranking updates to consumers
Application/Services/UCLRankingService/UCLRankingObserverService.cs - Schedule AppSvc · Coordinates schedule workflow and state updates
Application/Services/UCLScheduleMatchesService/UCLScheduleMatchesAppService.cs - Schedule Observer · Bridges schedule updates to consumers
Application/Services/UCLScheduleMatchesService/UCLScheduleMatchesObserverService.cs
Core
Shared contracts and models
- Ranking Contracts · Ranking service, state, observer, and manual/live contracts
Core/Interfaces/UCL/Ranking/IRankingServiceUCL.cs - Schedule Contracts · Schedule service, observer, and match contracts
Core/Interfaces/UCL/Schedule/IScheduleService.cs - General Contracts · Ping, settings, logging, and commentator contracts
Core/Interfaces/General/IPing.cs - Domain Models · Matches, teams, rankings, schedules, and shared results
Core/Models/Match/Match.cs
Infrastructure
Concrete services, integrations, and runtime configuration
- Ranking Infra · Live and manual ranking implementations
Infrastructure/Services/UCLRankingService/UCLRankingServiceLive.cs - Schedule Infra · UCL schedule and standing match implementations
Infrastructure/Services/UCLScheduleService/UCLScheduleService.cs - Ops Services · Logging, pinging, rescheduling, and commentator services
Infrastructure/Services/Logger/LoggerService.cs - Vizrt Client · Command builder and Vizrt-facing integration
Infrastructure/VizrtClient/VizrtCommandBuilder.cs - Runtime Config · Configuration objects and option settings
Infrastructure/Configurations/ConfigurationUCLRanking.cs
Build
Desktop packaging and CI
- Desktop Build · CI workflow, solution/project, and installer packaging
UCLMultileagueApp.sln
Connections 25
- App Shell → Main View: hosts · WPF shell loads the main view
- Main View → Main VM: binds to · View is driven by the main view model
- Main VM → UI Support: uses · View model relies on commands and UI helpers
- Main VM → Ranking AppSvc: invokes · Presentation actions trigger ranking workflows
- Main VM → Schedule AppSvc: invokes · Presentation actions trigger schedule workflows
- Ranking Job → Job Listener: notified by · Quartz job execution is observed centrally
- Schedule Job → Job Listener: notified by · Quartz job execution is observed centrally
- Ranking Job → Ranking AppSvc: runs · Scheduled ranking work enters the ranking orchestrator
- Schedule Job → Schedule AppSvc: runs · Scheduled schedule work enters the schedule orchestrator
- Ranking AppSvc → Ranking State: updates · Ranking orchestrator mutates shared ranking state
- Ranking AppSvc → Ranking Observer: publishes · Ranking changes are pushed through observers
- Schedule AppSvc → Schedule Observer: publishes · Schedule changes are pushed through observers
- Ranking AppSvc → Ranking Contracts: depends on · Orchestrator is defined by core ranking contracts
- Schedule AppSvc → Schedule Contracts: depends on · Orchestrator is defined by core schedule contracts
- Ranking State → Domain Models: stores · Shared ranking data uses core models
- Schedule Observer → Domain Models: emits · Schedule flow uses shared domain models
- Ranking Infra → Ranking Contracts: implements · Infrastructure provides ranking contract implementations
- Schedule Infra → Schedule Contracts: implements · Infrastructure provides schedule contract implementations
- Ops Services → General Contracts: implements · Operational services satisfy general contracts
- Ops Services → Runtime Config: reads · Operational behavior is configured at runtime
- Ranking Infra → Vizrt Client: drives · Ranking updates can be translated into Vizrt commands
- Schedule Infra → Vizrt Client: drives · Schedule updates can be translated into Vizrt commands
- Ranking Infra → Domain Models: maps · Implementation works with shared domain models
- Schedule Infra → Domain Models: maps · Implementation works with shared domain models
- Desktop Build → App Shell: packages · Build and installer target the desktop app entrypoint