How opendental/opendental works
Project Type and Purpose
• Open Dental is a full-stack, on-premises dental practice management application written in .NET/C# (WinForms or WPF) with a relational database back-end (typically MySQL or Microsoft SQL Server).
• It ships as a desktop client with an installer that creates and seeds the initial database, then runs the application against that local or networked database.
File Structure
• OpenDentalUI (Windows forms or WPF views)
• OpenDentalCore (business logic, domain objects)
• DataAccess or DAL (repository classes, SQL scripts)
• Reporting (Crystal Reports or similar)
• Services (background services, schedulers)
• Utilities or Helpers
• Installer files (WiX, MSI project)
• Config (app.config, connection strings, scripts)
• Build scripts or solution files (.sln, .csproj) and test projects will also appear.
README for Additional Insights
• It emphasizes installing the Trial Version first to provision the database schema.
• It references a central SVN repository for historical source and a programming resources page for DB documentation.
Main Components and Their Relationships
a. Client Application (UI)
• Windows Forms or WPF layers
• Entry points, menus, data grids, dialogs
b. Business Logic Layer (BLL)
• Domain services (e.g., patient management, appointment scheduling)
• Validation logic, business rules
c. Data Access Layer (DAL)
• Repository or TableGateway patterns
• SQL scripts and stored‐procedure calls
• Connection management
d. Database
• RDBMS (MySQL or SQL Server)
• Tables: Patients, Appointments, Claims, etc.
• Initial schema installed by the MSI installer
e. Reporting Engine
• Crystal Reports or built-in reporting module
• Report definition files (.rpt)
f. External/Infrastructure
• File system (for attachments, images)
• Network share (optional)
• Installer service (MSI/WiX)
• Version control (SVN server)
Architectural Patterns & Design Principles
• Layered Architecture (UI → BLL → DAL → Database)
• Repository pattern in DAL for DB interactions
• Dependency Injection for swappable components (configurable via app.config)
• MVVM or MVP if WPF is used
• Separation of concerns: keep UI, business rules, and data access decoupled
Versioning & Deployment Aspects
• Build process: source code → build server → MSI installer → Client + DB.