Welcome to the EZLogger project wiki!

EZLogger is a Microsoft Word VSTO Add-in built using VB.NET, WPF, and WinForms hosting. Its purpose is to help forensic analysts process reports more efficiently by automating metadata extraction, managing due dates, facilitating alert tracking, and assisting with document property population.

This wiki is intended for:

• Developers enhancing or maintaining EZLogger.

• Analysts curious about internal functionality.

• Future contributors seeking to understand the structure, conventions, and workflows.

EZLogger streamlines the forensic reporting workflow inside Microsoft Word by integrating:

• Patient identification automation (extraction of custom document properties).

• Due date calculation for critical Penal Code reports.

• Custom Task Lists to manage outstanding follow-ups.

• Alerting system based on patient or county-specific triggers.

• Seamless integration with SharePoint (via synced local folders).

• Support for PDF conversion and eventual metadata-driven document searching.

It maintains clean separation of concerns between UI, business logic, and data persistence using:

• Dedicated Handlers for form logic.

• Reusable Helper modules.

• DTOs for transferring structured data between logic and views.

Development adheres to a pragmatic semi-MVVM model customized for the constraints of VSTO.

---

Area	Approach
UI Hosting	WPF UserControls inside WinForms ElementHost
Core Language	VB.NET (.NET Framework 4.7.2)
Data Storage	Local SQLite database (for MVP), transitioning to SQL Server
Configuration	JSON files (local_user_config.json, global_config.json)
Office Integration	Word VSTO Add-in with Ribbon customizations
Git Repository	Private GitHub repo with potential for future Wiki/public expansion

---

• Follow Coding Standards for naming, error handling, and documentation.

• Before editing Helpers or Handlers, check if the feature is already covered.

• Propose major design changes via GitHub Issues or Discussions first.

---

• Configuration Management

• Task List and Alerts System

• Utilities and Reusable Helpers

"Build for the analyst, debug for the developer, document for the future." 🚀

---

---

You can start exploring by heading to the Setup Guide.

---

# EZLogger

Welcome to the EZLogger project wiki!

EZLogger is a Microsoft Word VSTO Add-in built using VB.NET, WPF, and WinForms hosting. Its purpose is to help forensic analysts process reports more efficiently by automating metadata extraction, managing due dates, facilitating alert tracking, and assisting with document property population.

This wiki is intended for:

• Developers enhancing or maintaining EZLogger.
• Analysts curious about internal functionality.
• Future contributors seeking to understand the structure, conventions, and workflows.

---

TBD

---

EZLogger streamlines the forensic reporting workflow inside Microsoft Word by integrating:

• Patient identification automation (extraction of custom document properties).
• Due date calculation for critical Penal Code reports.
• Custom Task Lists to manage outstanding follow-ups.
• Alerting system based on patient or county-specific triggers.
• Seamless integration with SharePoint (via synced local folders).
• Support for PDF conversion and eventual metadata-driven document searching.

It maintains clean separation of concerns between UI, business logic, and data persistence using:

• Dedicated Handlers for form logic.
• Reusable Helper modules.
• DTOs for transferring structured data between logic and views.

Development adheres to a pragmatic semi-MVVM model customized for the constraints of VSTO.

---

Area	Approach
UI Hosting	WPF UserControls inside WinForms ElementHost
Core Language	VB.NET (.NET Framework 4.7.2)
Data Storage	Local SQLite database (for MVP), transitioning to SQL Server
Configuration	JSON files (local_user_config.json, global_config.json)
Office Integration	Word VSTO Add-in with Ribbon customizations
Git Repository	Private GitHub repo with potential for future Wiki/public expansion

---

• Coding Standards article TBD
• Before editing Helpers or Handlers, check if the feature is already covered.
• Propose major design changes via GitHub Issues or Discussions first.

---

• (Configuration-Management)
• (Task-List-and-Alerts-System)
• (Utilities-and-Reusable-Helpers)

"Build for the analyst, debug for the developer, document for the future." 🚀

---