How serbanu/misyshackathon works
Project type and purpose
• This repo contains two separate Visual Studio solutions:
• ConsoleApplication1 – a .NET Framework command-line tool (ConsoleApplication1.csproj) that appears to perform I/O operations and handle “TablesCorrespondents” logic, using Npgsql for PostgreSQL connectivity.
• OutlookAddIn22 – a VSTO add-in for Microsoft Outlook (OutlookAddIn22.csproj) that hooks into Outlook events via the Office Tools runtime and provides custom functionality (PictureDispConverter, ThisAddIn.cs).
• The README simply labels it “MisysHackathon,” suggesting these are proof-of-concept/hackathon utilities rather than a single unified product.
File structure
• Each solution follows the standard VS layout:
· /<SolutionFolder>/*.sln, *.suo at root
· /<ProjectFolder>/*.csproj, *.Designer.cs, Properties/, Resources/
· /bin/Debug and /obj/Debug build outputs
• Key directories and files:
· ConsoleApplication1/IO_Operations.cs and TablesCorrespondents.cs – business-logic classes
· ConsoleApplication1/App.config – DB connection strings or other settings
· OutlookAddIn22/ThisAddIn.cs – entry point for the VSTO add-in
· OutlookAddIn22/PictureDispConverter.cs – custom utility class
· OutlookAddIn22/Properties/Resources.resx, Settings.settings – add-in configuration
README for additional insights
· Both projects reference .NET Framework assemblies.
· The console app references Npgsql (PostgreSQL driver).
· The add-in depends on Microsoft.Office.Tools.Outlook.v4.0 and the VSTO runtime.
Core components
a. Components
• ConsoleApplication1 (CLI application)
– IO Operations module
– TablesCorrespondents module
– Configuration (App.config)
– Data Access via Npgsql (.NET PostgreSQL driver)
• OutlookAddIn22 (VSTO add-in)
– ThisAddIn event handler (load/unload Outlook events)
– PictureDispConverter utility
– Resources & Settings for the add-in
– Dependency on Microsoft Office Tools runtime
• External Systems
– PostgreSQL database instance
– Microsoft Outlook application & COM interop / VSTO runtime
b. Relationships and interactions
– The console app reads from/writes to the PostgreSQL database using Npgsql and executes business logic in IO_Operations and TablesCorrespondents.
– The Outlook add-in runs inside Outlook, listens to mail/calendar events, invokes PictureDispConverter or other modules, and may also connect to the same database (if configured) or push data via a service.
c. Architectural patterns & design principles
– Layered architecture:
· Presentation layer (Console CLI vs. Outlook UI hooks)
· Business logic layer (IO_Operations, TablesCorrespondents, PictureDispConverter)
· Data access layer (Npgsql calls, App.config)
– VSTO Add-in pattern for Office extensibility
– Configuration-driven database connectivity
d. Relevant technologies/frameworks
– .NET Framework (C#)
– VSTO (Microsoft.Office.Tools.Outlook.v4.0)
– Npgsql (PostgreSQL .NET data provider)
– Visual Studio build outputs (.exe, .vsto)
Detailed breakdown to capture essential elements
• On the left, stack the ConsoleApplication1 layers:
[CLI UI] → [Business Logic: IO_Operations / TablesCorrespondents] → [Data Access: Npgsql] → [PostgreSQL DB]
• On the right, stack the Outlook add-in:
[Outlook Host (COM/VSTO)] → [ThisAddIn.cs (Event Handler)] → [Business Logic: PictureDispConverter] → (optional)[DB]
• Config files (App.config, Settings.settings) attached to each module
• Build artefacts (bin/Debug/*.exe, .vsto) as deployment outputs